Unplex provides a structured permission system to ensure efficient collaboration while maintaining control over user access. There are two levels of permissions: Account Level and Project Level. Below is an overview of each role and its associated permissions.
Account Roles
Beavr defines three distinct roles at the account level:
Admin – Full control over account settings, user management, and billing.
Member – Can create projects and collaborate but lacks administrative control.
Viewer – Has limited access and cannot create or manage projects.
Account-Level Permissions Overview
Permission Level | Account - Admin | Account - Member | Account - Viewer |
Manage account settings | ✅ | ❌ | ❌ |
Add/remove users at account level | ✅ | ❌ | ❌ |
Billing & subscription management | ✅ | ❌ | ❌ |
Create new projects | ✅ | ✅ | ❌ |
Access all projects in account | ❌ | ❌ | ❌ |
Role Descriptions
1. Admin
Admins have the highest level of authority within an account and can manage user access, settings, and billing.
Key Responsibilities:
Configure and manage account-wide settings.
Add or remove users at the account level.
Oversee billing, subscriptions, and integrations.
Use Case:
A firm’s IT administrator or managing partner handling system-wide configurations would typically have the Admin role.
2. Member
Members are active platform users who can create and manage projects but do not have administrative control over the account.
Key Responsibilities:
Create and participate in projects.
Collaborate within assigned projects.
Use Case:
A lawyer or paralegal working on case files within Beavr would typically be a Member.
3. Viewer
Viewers have restricted access and can only observe project content without the ability to create or modify projects.
Key Responsibilities:
View projects within the account.
Cannot create or manage projects.
Use Case:
A senior partner or external consultant who needs oversight of firm-wide activities without making modifications would be assigned the Viewer role.
Project Level Permissions
Project-level permissions define access within individual projects. A user's role at the account level does not automatically grant access to specific projects.
Project Roles
Beavr provides two project roles:
Editor – Can actively contribute by editing project content.
Viewer – Has read-only access to project materials.
Project-Level Permissions Overview
Permission Level | Project - Editor | Project - Viewer |
Manage project settings (e.g., permissions, integrations) | ❌ | ❌ |
Assign roles within a project | ❌ | ❌ |
Edit project content (documents, workflows, etc.) | ✅ | ❌ |
View project content | ✅ | ✅ |
Delete a project | ❌ | ❌ |
Role Descriptions
1. Editor
Editors are active collaborators within a project and can modify project content.
Key Responsibilities:
Edit project materials, including documents and workflows.
Work collaboratively on project deliverables.
Use Case:
A legal associate tasked with drafting and reviewing case documents would typically be assigned the Editor role.
2. Viewer
Viewers have read-only access to project content and cannot make modifications.
Key Responsibilities:
View project-related files, updates, and reports.
Cannot edit or manage project settings.
Use Case:
Clients or external auditors who need access to project documentation but should not alter its contents would be assigned the Viewer role.
Best Practices for Managing Roles in Unplex
1. Assigning the Right Roles
Admins should be limited to those responsible for overall account management.
Members should be users who actively work on projects.
Viewers should be assigned to individuals who only need oversight.
2. Handling Project Permissions
Editors should be assigned to team members who need to modify content.
Viewers should be used for external stakeholders who require visibility into project progress.
3. Security & Access Management
Regularly review user roles to ensure the right access levels are assigned.
Remove inactive users to maintain security and compliance.
Frequently Asked Questions
Can an Admin access all projects in an account?
No, Admins do not automatically have access to all projects. They must be explicitly added as an Editor or Viewer for specific projects.
Can a Viewer be upgraded to an Editor in a project?
Yes, a Viewer can be granted Editor access within a project by a Project Owner.
What happens if a Project Editor is removed?
The user will lose access to the project, but their contributions (documents, edits) will remain intact.