Skip to main content

Roles within the BIMcollab environment

This articles gives more insight in the different roles that are available in the BIMcollab environment.

Updated yesterday

BIMcollab offers a user structure that is designed to enhance collaboration and project management. User access and permissions can be managed by function, as well as project and project phase levels.

The user structure consists of three different levels, which are explained below.

⚠️ 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 required licenses

  • Administrator: Administrators have full control over the space, including managing users, projects, 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.

Info

💡 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. 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

Action

Project Leader

Editor

Editor for documents

Editor for issues

Reviewer for issues

Viewer

Add/edit Team members

Edit project settings

Create/Edit IDS **

View IDS **

View models in WebViewer

Add/Edit models in WebViewer

Permissions for Document Management

Action

Project Leader

Editor

Editor for documents

Editor for issues

Reviewer

Viewer

View documents

Download/ Add / Edit documents

Delete documents

Manual Publish *

Confidential docs *

(Optional)

(Optional)

(Optional)

(Optional)

(Optional)

View shared docs *

(Optional)

(Optional)

(Optional)

Add documents versions

View documents versions

Add/edit To Do

(+ Pdf annotations)

View To Do

(+ Pdf annotations)

Permissions for Issue Management

Action

Project Leader

Editor

Editor for document

Editor for issues

Reviewer

Viewer

View **

Comment **

Import/Export **

(Optional)

(Optional)

(Optional)

Add / Edit **

Delete **

(Optional)

Legend

  • = Role allows this action

  • = Role never allows this action

  • Optional = Can be enabled by project leaders or admins.

  • (*) = Requires CDE plan & license

  • (**) = Requires MQA plan & license
    Capabilities marked with (*) or (**) require an active license to be effective.

Once you have created or edited a team member, you have the option to add additional rights.

💡 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.

Did this answer your question?