Manage roles, capabilities, and access policies
Define job responsibilities and verify effective access before rollout.
Table of Contents
Who this is for: administrators who manage workspace access.
Use Roles to define capabilities, Capabilities to audit which roles hold them, Record access to inspect the record sets covered by role assignments, Deny rules to restrict access, and Policies to manage separation of duties. A role's name alone does not establish a person's effective record access or approval assignment.
Review existing roles
- Open Roles. Search by name and review Type, Classification, Members, and SoD rules.
- Open the role to read its capability grants and the people shown under Relationships. Member counts are derived from current assignments.
- Distinguish system roles from custom roles. Use the available actions for the role type; do not assume a system role can be edited like a custom role.
Create a role from a template
Use an Admin or Approver template, when offered, as a starting point for a custom role.
- Open Roles and use the option to create a role from a template.
- Choose the template and review its description, included capabilities and delegation information.
- Continue to the role form and enter an appropriate name and description.
- Review the classification and every selected capability. Adjust them to match the intended responsibility.
- Save the role, then grant it to the intended people or organizational units through the authorized access process.
Creating a role does not assign it. A template is a starting configuration; verify the effective access and record scope after granting the saved role.

Create a custom role
- Select New role.
- Enter Name and Description, then choose Job role or Privileged classification.
- Use Search capabilities and select the specific permissions needed. Read each description and review the selected count.
- Review the intended duties before selecting Save role. The role is available for assignment as soon as it is saved.
- Assign it through the authorized person or org-unit access process. Creating a role is different from assigning it.
A role with no selected capabilities can be saved, but its holders gain no capabilities from that role. Broad permissions, such as reading any submission or managing all tasks, require particular care. The capability descriptions can also identify dependencies and limitations.

Audit capability grants
Open Capabilities to inspect which roles hold a capability. Compare this view with the person's role assignments and the resource scope. For reviewers, check both the ability to decide and eligibility to be seated by a workflow, as well as the current assignment.
Configure record access
The current interface separates Record access, Deny rules, and Policies. If your workspace shows an earlier layout, confirm its available controls with your administrator.
- Open Record access to inspect the record sets that role assignments cover. Search by name or a condition value; use Unused or the sorting controls as needed.
- Review Records where, Used by, Version, Evaluation, and State. Check dependent assignments before changing a shared set.
- To define a set, select New record set, enter a name, and use Add condition. The screen groups conditions under “Records where all of these match.” Review the intended scope before saving.
- Verify the role assignment that uses the set. Creating a record set alone is not proof that a person has access.

Deny access to selected records
Deny rules hides matching records from specified people or org units, subject to the exceptions shown in the interface.
- Open Deny rules → New deny rule and enter a name.
- Define the fixed-value conditions under Hide records where all of these match. You can copy conditions from a record set; this copies the values only, so later edits to that set do not update the deny rule.
- Select the people or org units covered by the rule.
- Review the exceptions: covered people still see records they submitted, own, or responded to. They are not told about the rule. If a covered person is an approver on an open stage, the interface states that they are skipped and the stage is reassigned.
- Save only after reviewing the intended restriction: the rule takes effect immediately. Test both an included and an excluded person.

Manage separation of duties
Use Policies → SoD Rules to review the workspace's rules. Coordinate rule and risk decisions with the responsible access owner. Under SoD Settings, review whether risk acceptances never expire or use a validity period, and configure the advance expiry warning before selecting Save settings.
Verify effective access
- Check a user who should be included and one who should be excluded.
- Test record reading, submission, and approval as separate tasks.
- Check relevant unit memberships, role assignments, scopes, and access-rule conditions when a menu or record is missing.
- Use Check access to choose a person, enter a record reference, and optionally specify an As of date. Inspect the result for that person and record. Audit log → Live access provides a separate current-access view.
- Review the audit trail after an authorized access change.
See Create and maintain organizational units and memberships for hierarchy and rule-managed membership.
