Users and Groups

OpenProcess - Creating Groups

OpenProcess - 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 (with example Groups):

mceclip0.png

 

To add a Group, click 'Add a new group' and the following screen is presented:

mceclip1.png

 

You need to give the Group a name and description as well as at least one permission.

Permission

What does it permit

User administration

Ability to create/modify users

Organisation administration

Ability to create/modify organisations

Group administration

Ability to create/modify groups

Process definition administration

Ability to create/modify processes

Start a process

Ability to manually start a process

Work on a step

Ability to complete assigned tasks

Read attributes via stamp

Not relevant for users

Subject access

Not relevant for users

Step administrator

Ability to oversee Tasks for any step in a process assigned to a Group with this permission

Process read

Not relevant for users

Service area administration

Ability to create/modify Service Areas

Document type administration

Ability to create/modify Document Types

View document backlog

 

 

 

                                          

Ability to view the items imported automatically into the Document Backlog.  The user would need the “Start a process” permission too if they were to need to start processes based upon an item imported automatically.

Document template administration

Ability to create and edit document templates for outgoing correspondence.

Account extract administration

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

Search processes

Ability to access the “Search Processes” function that allows one to see processes that are both in progress and completed.

Continue processes

For sites that have the integrated Revenues forms, allows users to click on “continue process” function.

Administer document backlog

Ability to set up different indexing queues for the Document Indexing function.

Api administrator

Ability to access the API setting in the Set Up Screen

 

 

As an example, the following might be typical Groups and the associated permissions in a Council:

Group

Permissions

Scanning and indexing team

·        View document backlog

·        Start a process

Caseworkers

·        Work on a step

Caseworker supervisors

·        Work on a step

·        Step administrator

Systems administrators

·        User administration

·        Organisation administration

·        Group administration

·        Document type administration

·        Document template administration

·        Account extract administration