Permission Sets

Permission Sets

How to create and edit permission sets that define granular module-level access in the Clew Platform

Contents

• 1. Introduction & Context
• 2. Key Features & Functions
• 3. Requirements
• 4. Step-by-Step Guide
  • Creating or Editing a Permission Set
  • Setting the Permissions
• 5. Common Issues & Troubleshooting
• 6. Related Articles

1. Introduction & Context

Permission sets are the foundational component for user access to data in the Clew Platform, letting you define very granular permissions per module for a group of users. For example, a group of users may be able to view incidents, view and update risks, and have full access to actions on a single register.

A permission set by itself does not grant users access to anything in the platform. It must be applied against a register through a security group, which is where user groups are configured.

Who is it for? System Administrators who configure access control in the Clew Platform.

What does it impact? Permission sets define what actions users can perform per module. Changing an existing permission set affects every user in the security groups where it is used, so changes should be made with care.

2. Key Features & Functions

• Permissions per module: permissions are granted per module in the platform, so each module can have a different level of access within the same set.
• Seven permission types: Create [C], Read [R], Update [U], Delete [D], Mass [M], Merge [M], and Share [S], described in the table below.
• Flexible configuration: set all permissions in one go, per module, or per individual permission within a module.
• Global option: one permission set may be marked as global, applying its permissions to all users and all registers.

3. Requirements

• System Administrator access is required to configure permission sets.
• A permission set by itself does not grant users access to anything. It requires security groups to be configured, where the permission set is applied against a register (or folder) in the platform.
• There is one exception to this rule: one (1) permission set may be marked as global, which applies the permissions to all users in the platform. A good example is allowing all users to create a declaration or an incident.
• Exercise care when changing existing permission sets, since they may be in use and changes will affect users in the groups where the permission set is applied.

4. Step-by-Step Guide

Creating or Editing a Permission Set

1. Navigate to Admin > Permission Sets. This opens a list of existing permission sets.
2. If creating new, select Add. If editing an existing set, select the title of the permission set and proceed to step 4.

The Permission Sets list. Click Add to create new, or a title to edit.

3. Once completed, press Save to proceed to setting the permissions up.

The permission set form with the fields described above.

Setting the Permissions

4. On this page, you will see the module permission sets. Any modules available are displayed with a grey header, while any disabled modules are displayed with a pink header. You can set all permissions in one go, per module, or per permission per module.
5. To set a permission for an entire module, select the shield button on the module permission set header, as shown below. This enables (or disables) all permissions in one click.

The shield button on the module header enables or disables all permissions in one click.

6. Alternatively, click the shield next to an individual permission to enable that permission type only. The screenshot below shows Create, Read, and Update enabled for Actions.

Create, Read, and Update enabled for Actions using the individual permission shields.

5. Common Issues & Troubleshooting

Best practices:

• Give permission sets clear titles that describe the access they grant, so they are easy to identify when configuring security groups.
• Use the Details field to record the intended purpose of the set for future reference.
• Keep the Global permission set minimal. It applies to every user and every register, so it should only contain permissions everyone genuinely needs.
• Check which security groups use a permission set before editing it, as changes take effect for all users in those groups.

6. Related Articles

• Security Groups
• Deleting Records
• Sharing Items