As a Brand, you can now assign permissions for specific actions within Assessments, Audits, and CAP, in addition to the existing module-level access. Each module opens into a list of individual actions, so you can choose exactly what each role can do. For example, a reviewer can approve sections and flag non-conformities without being able to launch or cancel requests.
For example, in Assessments, permissions are grouped into viewing (requests, responses, activity, and CAP), launching and managing requests, reviewing responses, and finalization and CAP. The existing Read Only, Full Access, and No Access settings remain available as one-click presets. You can apply a preset and then switch individual permissions on or off, alongside Select All and Select None shortcuts.
Some permissions depend on others being granted first. If a prerequisite has not been selected yet, the permission that depends on it stays disabled. If you remove a prerequisite that other permissions depend on, you are notified first, and those dependent permissions are removed along with it. This dependency check also applies when saving, a role cannot be saved if any permission is missing a prerequisite it needs.
Key Benefits for Brands
- Precise Role Design: Build a role around exactly the actions a user needs.
- Limited Access to Sensitive Actions: Restrict actions such as cancelling, locking, or starting a CAP to the right people, which lowers the risk of mistakes.
- Clear Separation of Duties: Keep review, launch, and finalization responsibilities with different people.
- Guided, Error-Free Configuration: Presets give you a starting point, and dependency enforcement prevents you from saving a role that would leave a user with an action they cannot actually use.
This update adds action-level permissions to Assessments, Audits, and CAP, on top of the existing module-level settings, giving brands precise control over what each role can do.
Documented in: You must log in to the platform to access the below links.
Brand Guide |