BIMcollab offers a user structure that is designed to enhance collaboration and project management. User access and permissions can be managed by space function, as well as project and project phase levels.
Space level roles
BIMcollab roles are organized into distinct levels based on their scope of actions:
Space level roles
Project Team Member roles
Phase level roles
⚠️ Note: Not all features are available on all Tiers. To check if it’s included in your subscription, review the [Tier comparison list] or contact your admin. If a feature isn’t available, you may need to upgrade your tier.
Space level roles
These roles determine a user's administrative access to the entire BIMcollab space. They apply to all solutions included in your subscription. Which users will have access to which solutions are managed by assigning a required licenses (Nexus, twin and Zoom).
Administrator: Administrators have full control over the space, including managing users, projects, document management (metadata, workflows, document naming convention, work packages) and subscription details.
Regular User: By default, regular users do not have any administrative rights. Their permissions are determined by their project and team roles.
📝 Note: By default, only space administrators can add new users to the space. However, administrators can give users the right to create new projects and add new users to the space. In this way, certain users do not have access to the space and subscription settings, but can still create projects and users.
💡 Tip: Learn how to add a new user to your BIMcollab space in this article.
Project team member roles
At the project level, a team member has access to issues and documents, but they do not have access to documents at the phase level (unless they are also a part of a project phase team). Since this role is specific to the project, a user can hold different team member roles for each project in which they participate.
💡 Tip: You can quickly see your project-level role on the My projects tab in the web application.
Below, we can see the project team roles and their permissions on the project level:
General permissions
General permissions define what users are allowed to manage within the overall project settings, such as general project settings, team members, managing IDS specifications, and working with models in the WebViewer.
Action | Project leader | Editor | Editor for documents | Editor for issues | Reviewer for issues | Viewer |
Team members | ☑️ | 👁️ | 👁️ | 👁️ | 👁️ | 👁️ |
General project settings | ☑️ | ✖️ | ✖️ | ✖️ | ✖️ | ✖️ |
IDS | ☑️ | 👁️ | 👁️ | 👁️ | 👁️ | 👁️ |
Models in WebViewer | ☑️ | ☑️ | ☑️ | 👁️ | 👁️ | 👁️ |
Permissions for Document management
Document permissions determine what actions users can perform in document management.
Action | Project leader | Editor | Editor for documents | Editor for issues | Reviewer for issues | Viewer |
Documents | ☑️ | ☑️ | ☑️ | 👁️ | 👁️ | 👁️ |
Download documents | ☑️ | ☑️ | ☑️ | ✖️ | ✖️
| ✖️
|
Delete documents | ☑️ | ✖️ | ✖️ | ✖️ | ✖️ | ✖️ |
Manual approval | ☑️ | ☑️ | ☑️ | ✖️ | ✖️ | ✖️ |
Confidential documents * | ☑️ | ☑️ (Optional) | 👁️(Optional) | 👁️(Optional) | 👁️(Optional) | 👁️(Optional) |
View shared documents | ☑️ | ☑️ | ☑️ | 👁️(Optional) | 👁️(Optional) | 👁️(Optional) |
Documents versions | ☑️ | ☑️ | ☑️ | 👁️ | 👁️ | 👁️ |
Edit document metadata | ☑️ | ☑️ | ☑️ | 👁️ | 👁️ | 👁️ |
Document revisions* | ☑️ | ☑️ | ☑️ | 👁️ | 👁️ | 👁️ |
To Do | ☑️ | ☑️ | ☑️ | ☑️ | ☑️ | ☑️
|
PDF Annotations | ☑️ | ☑️ | ☑️ | 👁️ | 👁️ | 👁️ |
Permissions for Issue management
Issue management permissions control how users interact with issues, as well as permissions for issue approval, import/export, deleting issues and setting issue properties.
Action | Project Leader | Editor | Editor for document | Editor for issues | Reviewer for issues | Viewer |
Issues | ☑️ | ☑️ | 👁️ | ☑️ | 👁️ | 👁️ |
Comment | ☑️ | ☑️ | ☑️ | ☑️ | ☑️ | 👁️ |
Assigned to issue Approval* | ☑️ | ☑️ | ✖️ | ☑️ | ☑️ | ✖️ |
Import /Export | ☑️ (Optional) | ☑️ (Optional) | ✖️ | ☑️ (Optional) | ✖️ | ✖️ |
Delete | ☑️ (Optional) | ✖️
| ✖️
| ✖️
| ✖️
| ✖️
|
Set issue properties | ☑️ | ✖️ | ✖️ | ✖️ | ✖️ | ✖️ |
Has Zoom edit rights* | ☑️ (Optional) | ☑️ (Optional) | ✖️ | ☑️ (Optional) | ✖️ | ✖️ |
Legend
☑️ = Add/Edit/View permissions
👁️ = Only View permissions
✖️ = No permissions
Optional = Can be enabled by project leaders or admins.
(*) = Depends on your tier.
💡 Tip: Adding a new team member and assigning additional rights is explained in detail in this article.
Phase team roles (Document Management)
⚠️ Note: These roles are not available on all Tiers. To check if it’s included in your subscription, review the [Tier comparison list] or contact your admin. If the role isn’t available, you may need to upgrade your plan.
In the CDE, projects can be managed at both the project and project phase levels. When working at the phase level, users are added to Phase Teams and assigned a specific user role within that phase.
These roles are custom-defined by the space administrator, who also assigns User Rights to each role. These rights determine what actions users can perform and what data they can access within each phase, ensuring that team members only see and do what’s relevant to their responsibilities.
💡 Tip: User role permissions, which manage user access on the project phase level only, are explained in detail in this article.

