security-noteDifficulty: beginnerTime: 15mVersion: v1Reviewed: 2026-07-14Reviewer: Access Control ownerTags: help, admin-security, access-control
Set RBAC and Matter Permissions
Apply role and matter-level policies to enforce legal-need access boundaries.
Overview
Apply role and matter-level policies to enforce legal-need access boundaries.
Audience
- Admin
- It Security
Product Area
Access Control
Prerequisites
- Users invited
- Branch structure configured
Steps
- Assign base roles
Use predefined roles for partner, associate, compliance, and readonly users.
- Apply matter ACL
Grant explicit matter access and activate ethical-wall restrictions for conflict-sensitive matters.
Expected Result
The Access Control workflow completes without unresolved validation errors, and the result is visible to the intended roles.
Security and Audit Notes
- Use the least-privileged role that can complete the task.
- Confirm the resulting change or decision appears in the workspace audit trail when the workflow changes customer data or access.
Limits and Preconditions
- Available controls depend on the tenant plan, enabled modules, jurisdiction, and administrator policy.
- If a named control is not visible, confirm entitlement and role access before treating the behavior as a product failure.
Troubleshooting
- Relying only on role permissions: Always enforce matter ACL as second gate.
Related Articles
Escalation
If the documented result cannot be reached after the checks above, capture the workspace identifier, affected product area, timestamp, and a redacted error message, then use Support. Never include secrets, privileged legal content, or customer documents in the initial report.