In CLM, what is the relationship between Roles and Permissions?

• A. Roles define permissioned capabilities and responsibilities within the workflow.
• B. Permissions define the roles rather than vice versa.
• C. Roles are only for display; permissions are separate.
• D. Permissions are not used in workflow design.

Answer: (A)

Roles encapsulate what a person can do and their responsibilities in the contract workflow. In CLM, permissions are the specific actions that can be taken (view, edit terms, route for approval, sign, etc.). A role is defined by the collection of permissions it includes plus the duties tied to that role. When you assign a user to a role, they inherit those permissions for the contracts they work on, enabling them to perform their tasks within the workflow. This arrangement keeps security and process control consistent, because adjusting the permissions attached to a role automatically updates all users in that role. For example, a contract owner might be able to edit and route, while a signer can apply a signature without altering terms.