Permissions Matrix
Last updated: May 21, 2026
Background
Document Crunch uses a role-based permissions model that controls what each user can see and do across your organization. Permissions are scoped at the Organization, Team, and Project levels, and each role is designed to reflect real-world responsibilities — giving your team the access they need without overexposing sensitive content.
Use this article as a quick reference to understand which roles are required to perform specific actions in Document Crunch.
Things to Consider
There are four active roles in Document Crunch: Organization Admin, Team Admin, Team Editor, and Team Viewer
Organization Admins have the broadest level of access and can manage all teams and content within the organization
Team Admins manage their own team(s) — they cannot modify Organization Admins or act outside their assigned teams
Team Editors and Viewers cannot manage users or settings, but Editors can create and work with content
All roles — including Team Viewers — can view, chat with, and share content
At least one Organization Admin and one Team Admin must exist at all times; the system will block any action that would remove the last admin of either type
Project-level roles (Project Admin, Project Editor, Project Viewer) are planned for a future release and are not yet available
Permissions Matrix
User Management
Action | Org Admin | Team Admin | Team Editor | Team Viewer |
Invite users to the organization | ✓ | — | — | — |
Invite users to a team | ✓ | ✓ (own teams) | — | — |
Grant / revoke Org Admin | ✓ | — | — | — |
Grant / revoke Team Admin | ✓ | ✓ | — | — |
Move users between teams | ✓ | ✓ (own teams) | — | — |
Remove users from a team | ✓ | ✓ (not Org Admins) | — | — |
Remove users from the organization | ✓ | — | — | — |
Teams & Settings
Action | Org Admin | Team Admin | Team Editor | Team Viewer |
Create teams | ✓ | — | — | — |
Edit / rename teams | ✓ | ✓ (own teams) | — | — |
Delete teams | ✓ | ✓ (own teams) | — | — |
Rename organization | ✓ | — | — | — |
Access Org Settings | ✓ | — | — | — |
Access Team Settings | ✓ | ✓ | — | — |
Note: At least one team must exist at all times. The system will prevent deletion of the last remaining team in an organization.
Content & Projects
Action | Org Admin | Team Admin | Team Editor | Team Viewer |
Access all teams' content | ✓ | — | — | — |
Create projects | ✓ | ✓ | ✓ | — |
Delete / archive projects | ✓ | ✓ | — | — |
Upload, move, or delete documents | ✓ | ✓ | ✓ | — |
Apply / remove playbooks & reviews | ✓ | ✓ | ✓ | — |
Create markups & version comparisons | ✓ | ✓ | ✓ | — |
View content | ✓ | ✓ | ✓ | ✓ |
Chat with content | ✓ | ✓ | ✓ | ✓ |