Purpose
Permission sets are the foundational component for user access to data in the platform. This is where you can be very granular about what permissions a user group can have. For example, a group of users may be able to view incidents, view and update risks, and have full access to actions to a single register.
- Ability to set permissions per module: Allows permissions to be granted per module in the platform.
- Types of permissions: Create [C], Read [R], Update [U], Delete [D], Mass [M], Merge [M], Share [S].
| Permission Type | Description |
Create [C] | Ability to be able to create |
Read [R] | Ability to be able to read the item/s |
Update [U] | Ability to edit the item via ‘Manage -> Edit’ |
Delete [D] | Ability to delete, find more information here. |
Mass [M] | Mass works in conjunction with Update and Delete. If ‘Mass’ is selected, as well as Update, then the permission set will grant Mass Update. |
Merge [M] | Only relevant to Library Control, Library Cause, and Library Consequence. Ability to merge them together. |
Share [S] | Ability to share items, find more information here. |
Important Notes
- System Administrator access is required to configure permission sets.
- A permission set by itself does not grant users access to anything in the platform. It requires user groups to be configured (in a group, a permission set is applied against a register – or folder – in the platform). This user groups are referred to as security groups.
- There is one exception to this rule, one (1) permission set may be marked as global and this will apply the permissions to all users in the platform. A good example is all users can create a declaration or an incident.
- Please exercise care when changing existing permission sets since they may be in use and it will affect users that are in groups where the permission set is used.
Caution: Global Permission set grants the selected access to all registers.
Step by Step Guide to Create or Edit a Permission Set
- Navigate to Admin > Permission Sets. This will open a list of existing permission sets.
- If Creating new, select ‘Add’
If Editing existing, select the title of the permission set. Proceed to step 4.

| Field | Description |
Title | Used to select within a group (256 character limit) |
Details | Visible only within Permission Set list view. (25000 character limit) |
External ID | Used only for API integration |
Global | If yes, grants the permission set to all users, and to all registers. Only one permission set can be global. |
3. Once completed, press save to proceed to setting the permissions up

4. On this page, you will see the following main components:
- Module permission sets. Any modules available will be displayed with a grey header. Any modules disabled will be displayed with a pink header.
- You can set all permissions in one go, or per module, or per permission per module.
5. In order to set a permission for an entire module, please select the “shield” button on the module permission set header as shown below:

Here you can enable all permissions in one click (or disable them all).
Alternatively, you can click the shield next to the permission to enable an individual permission type. The screenshot below shows Create, Read, and Update for Actions.

Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article