How are Permissions Determined for Custom Roles?
Permissions for custom roles are determined based on the role type you select. These permissions are highly flexible and can be tailored to suit your specific use cases. Here's a breakdown:
For Example, Let's Consider the Compliance Admin Role:
Default Permissions: The Compliance Admin role comes with default permissions for Orchestration, Compliance, Governance, Admin, Automation, and Reports.
Customization: You have the freedom to edit these permissions to precisely control what a user can do within each of these categories. You can specify whether a user can edit, create, delete, or simply read specific modules.
Similarly, for the Finance Role:
Default Permissions: The Finance role includes default permissions for Orchestration, Governance, Self Service, and Reports.
Customization: Just like the Compliance Admin role, you can customize these permissions to define the exact capabilities of users within each module.
Additionally,
Reports: 'Reports' is a common option available in both roles. However, it's essential to understand that 'Compliance Admin' will have access to specific types of reports tailored to their role.
For Compliance Admin:
For Finance:
These sub-options and permissions can be finely tuned to align with your unique requirements and organizational structure.