This article brings together all of the user groups described across the product documentation.
These user groups are generally defined in the workflow processes used by products, so users will need to be in these groups to start the relevant processes.
| Assisted Service | |
|---|---|
| SECURED | Users in this group can start the interaction log |
| Bookings - Diary Planner/Slot Bookings | |
| SLOTBOOKINGADMIN | The admin user group which by default has access to the dashboards. This group is named (and could be changed) in the Core Slot Bookings Settings |
| SLOTBOOKINGUSER or CITIZENS | Users, including the anonymous user, need to be in these groups to make bookings. This grouped is named (and could be changed) in the Core Slot Bookings Settings |
| Bookings - Events | |
| BOOKANDPAYADMIN | These users create and schedule occurrences |
| BOOKANDPAYCASHPAYMENT | Some users are able to make/take cash/offline payments. The name of this group is set in the cashPaymentGroup property of the configuration end point. See Payments |
| BOOKANDPAYUSER | Users, including the anonymous user, need to be in this group to make bookings |
| Bookings - Registrars | |
| SLOTBOOKINGADMIN and SLOTBOOKINGUSER | These groups have the same functions as the core Diary Planner product above |
| CSA_GENERAL | Has read only access to the calendars and can search for appointments |
| SLOTBOOKINGREGISTRAR | Can create and manage bookings via the calendars and use the forms to handle Requests from Other Offices |
| Bookings - Room Bookings | |
| CONTRIBUTE | Users in this group can create rooms using the contribute form |
| ROOMBOOKINGADMIN | These users are responsible for approving bookings and can also cancel and amend bookings. When you create a room you can pick the administrator user group (in the contribute form) which maps to one or more site user groups (see Room Managers in Configuration and Users) |
| ROOMBOOKINGUSER | When you create a room you can set (in the contribute form) these are the users who can book it. This group is the default |
| Case Management | |
| The user groups able to work on a case are set in the configuration of each case type. The groups below are root/holding groups. See group configuration and Standard Articles and User Groups for more information | |
| CM-CASES | The general group for case manager users, sub divided into case types |
| CM-TASKS | Users in this group can have tasks assigned to them. May be sub divided by case or task type |
| CM-USERS | A container for the two main non-manager user groups which includes system users |
| CM-CONFIGURATORS | Users who can use the configuration forms to create new cases and tasks |
| CM-STARTERS | The users who can raise cases. Normally this should include group(s) for registered users and the anonymous user. If members of staff are allowed to raise cases, then include them too |
| Contribute | |
| CONTRIBUTE | Users need to be in this group to create content using the contribute forms |
| CONTRIBUTEARTICLE_APPROVALCANDIDATEGROUP | Not the name of a user group, but a variable set in the contribute form. The user group you set here will be responsible for approving content |
| CONTRIBUTEARTICLE_CANDIDATEGROUP | Not the name of a user group, but a variable set in the contribute form. The user group you set here will be able to claim and work on the update, archive and copy tasks |
| Data Export Manager | |
| DATAEXPORTER | The data exporter is designed to be used as an iCM Form App. Your iCM user should be aliased to a site user in this group |
| Multiple Payment Basket | |
| CITIZENS, PUBLICONLY or SECURED | Users in these groups can use the payment basket |
| Payment Reconciliation | |
| PAYMENT RECONCILIATION | If you enable payment reconciliation, any user that needs to make a payment, including the anonymous user, needs to be in this group |
Last modified on 18 March 2024
Share this page
