Users and Groups

Groups

Groups are an effective way of being able to associate a set of permissions with a given user role. For example, if one creates a super user group one might give them lots of permissions and only users with this group associated with their user will have access to all of the permissions.

 

If another user also needs to be a super user it is just a case of assigning them to the super user group rather than having to pick and choose the permissions they should have. Likewise an officer may simply have permission to work on tasks but that's it.  So you could create a group of officers specific to case management and this could easily be assigned to many users. As the permissions that can be assigned are fixed and groups are required to be assigned to users it makes sense to create groups first.

 

The following illustrates the Groups screen:

blobid0.png

 

These are the existing groups for IEG4 council. To add a group one needs to click ‘Add a new group’ and the following screen is presented: 

 

blobid1.png

 

It is necessary to give the group a name and description as well as at least one permission. 

 

The following explain each permission: 

User administration  

One to be able to create/modify users 

Organisation administration  

One to be able to create/modify organisations 

Group Administration  

One to be able to create/modify groups 

Start a process  

One to be able to create/modify processes 

Work on a step  

One to be able to adhoc kick off a process 

Read attributes via stamp  

Not relevant for users 

Subject access  

Not relevant for users 

Step administrator 

Enables the user to be able to supervise steps 

Access reporting 

The ability to access OpenProcess Reporting in the Reportal 

Process read 

Not relevant for users 

Service area administration 

One to be able to create/modify service areas 

Document type administration  

One to be able to create/modify document types 

View document backlog  

One to be able to view the items imported automatically following scanning. The user would also need the ‘Start a process’ permission if they had the job of indexing and kicking off processes too. 

Document template administration  

The ability to create and edit document templates for outgoing correspondence. 

Account extract administration  

The ability to create and edit Account Extracts used for indexing of documents and processes 

Search processes  

The ability to access the Search Processes function that allows one to see processes that are both in progress and completed. 

Continue processes 

The ability for users using the Revenues Process Orchestration functionality to be able to restart a process that is paused. 

Administer document backlog 

The ability to carry out activity in the backlog 

Api Administrator 

The ability to access the API Developer area and create API keys.