You can restrict users from saving role information in the Role section of the Contacts module by adding the permission level rule /britecore/contacts/storeRoles. When a user with this permission level rule tries to edit and save information in the Role section of the Contacts module, an Error pop-up window opens stating, You don’t have permissions to complete the requested action.
To add the permission level rule:
- Navigate to Settings > System Wide > Permissions.
- In the Permission Levels section, select the pencil icon next to the permission level you want to add the rule to, such as Employee or Underwriter.
Note: If you don’t see the permission level you want to add the rule to, you may need to first add the permission level. See Add permission level.
- Select + Add a rule to add a new rule.
- In the Access column, select the None radio button.
Note: If you select the Read/Write radio button, the user will continue to have access to adding roles in the Contacts module.
- From the Rule dropdown list, select /britecore/contacts/storeRoles. BriteCore will automatically save the new rule.
- In the Role Permissions section, ensure the role that matches the permission level you added the rule to is assigned the correct permission level. For example, if you added the rule to the Employee permission level, ensure that Employee displays in the Employee Role Permissions dropdown list.
Usage considerations
Permission levels can also be set at the contact level in the Contacts module. See Permissions version 1 overview to learn more about the interaction between permission levels set at the role level and permission levels set at the contact level.
Related Settings
Advanced Setting: restricted-roles-on-store-contact-name
This setting allows you to define specific roles that should be restricted from modifying the storeContactName permission. You can specify the roles in a comma-separated list.
How It Works:
- The restricted-roles-on-store-contact-name setting blocks specified roles from having access to modify storeContactName.
- BriteCore assumes permissions are granted by default. This means roles that are not explicitly restricted by the restricted-roles-on-store-contact-name setting (such as those without an explicit restriction on britecore/contacts/role/Administrator will retain admin write permissions.
- The Administrator role has precedence over the storeContactName setting. If a role has admin write permissions, it can override the restrictions set on the storeContactName.
Example:
- If you add the role Underwriter to the restricted-roles-on-store-contact-name setting, users with the Underwriter role will not be able to modify the storeContactName, even if they are granted other permissions.