How it works
Use available roles to organize basic resource access. Give participants the access they need to view, comment, edit, or manage work without sharing administrator accounts.
A concrete business example
Choose an appropriate role for a reviewer, then verify its behavior using that account. Do not assume the role name alone establishes the required boundary.
How it supports people and agents
Treat tool credentials as delegated access with a named owner. Keep an agent's capability, responsibility, and permissions distinct.
Core scope and boundaries
Basic roles do not establish fine-grained record or field policies, independent approval rights, or a complete agent authorization engine.
Start with a real case
- List the participants and the resources needed for their responsibilities.
- Verify the behavior using a non-administrator account and realistic records.
- Document access and retention limits and test the intended recovery procedure.
Core product guide: these pages explain foundational capabilities and configurable application patterns. Integrations and the selected product release require validation. Enterprise automation, fine-grained governance and independent verification are separate scope.