Platform capability
Access Under Control
Strong permissions mean users see only what they are allowed to see.
At a glance
Each user sees only what their role allows. Permissions apply to each document and each feature, and search respects them too.
Key Takeaways
- Strong access controls mean users only see the documents and data they are allowed to see.
- Control access to individual documents or document collections.
- Only approved team members can see sensitive deal details.
Technical details
Role-based access control (RBAC) sets who can open each document and use each feature. You can base rules on a user's role, team, document class or other custom attributes. The system supports both role-based and attribute-based access control (ABAC), so you can set very precise permissions.
Benefits
- Document-Level Security: Control access to individual documents or document collections.
- Workspace Roles: Owner, Admin, Member and Guest roles control who can see and change what in each workspace.
- Attribute-Based Rules: Go beyond roles with rules based on user and document attributes.
- Inheritance & Delegation: Permissions pass down through levels, and you can hand rights to others.
Questions answered
What does Role-Based Access Control do?
Strong access controls mean users only see the documents and data they are allowed to see.
How does the capability work inside OdysseyGPT?
Role-based access control (RBAC) sets who can open each document and use each feature. You can base rules on a user's role, team, document class or other custom attributes. The system supports both role-based and attribute-based access control (ABAC), so you can set very precise permissions.
Where does it deliver operational value?
Confidential Matters: Only approved team members can see sensitive deal details. Client Segregation: Only the staff assigned to a client can see that client's data. Departmental Boundaries: Keep walls between departments or practice groups.