Do you have questions about how to manage permissions for your team in both the Workplace and the Projects?
This guide explains how predefined roles work and how permissions can be configured to ensure the right level of access for every user.
BIMWorkplaces provides predefined, non-editable role levels for both the Workplace and the Projects. Workplace managers can also create custom roles when needed.
Workplace Roles
The Workplace includes three fixed roles:
- Standard
- Guest
- Admin
These roles come with predefined permissions that cannot be modified.
Workplace Managers may create additional custom roles, assigning each permission level as required.
Project Roles
Projects also include three fixed roles:
- Standard
- Guest
- Project Manager
These roles and their permissions are fixed and cannot be changed.
Permission Levels
Each role – predefined or custom – is composed of a set of permissions.
Every permission can be configured with one of the following levels:
- None:
The user cannot view or access the feature. Buttons, tabs, and actions related to this permission will not be visible.
- Read:
The viewer can view information but cannot make changes.
- Total:
The user can view, edit, and delete information.
Topic-Related Permissions
Within the Collaboration module, three permissions require special attention, as they control how users interact with public, private and closed topics.
As explained above, predefined roles cannot be modified.
However, these three specific permissions can be overridden even for Project Managers, by creating a custom role.
To override these permissions for Project Managers:
- Create a New project role.
- Keep all permissions set to Total, except the three topic-related permissions you wish to chance.
- Select the new role and click Mark as Manager in the ribbon. This applies the custom role settings to all Project Managers in this project.
- To restore the default Project Manager behaviour, select the custom role again and click Unmark as Manager.
This mechanism allows flexibility while preserving the integrity of the default permission model.
- Manage public topics
Controls the ability to modify public topics created by other users.
- None -> User cannot modify public topics unless explicitly granted permissions inside the topic (click here for more information)
- Read -> User may view public topics, but cannot change them unless explicitly granted permissions
- Total -> User may edit and delete any public topic
- Manage private topics
Controls access to private topics created by others.
Important: Changing this permission removes the guarantee that private topics remain private. Use with caution.
- None -> User cannot see private topics unless explicitly included in their permissions
- Read -> User may view private topics, even without explicit access
- Total -> User may edit or delete private topics, even without granted permissions
- Closed topics
Controls the use of the ‘Closed Topic’ feature (click here for more information)
- None -> The ‘Closed Topic’ functionality is disabled for the project.
- Read -> User can close a topic, but closing does not change permissions; users who could edit before will still be able to edit
- Total -> User can fully close a topic, locking the topic from further modification. All users become read-only and no additional edits are allowed.
With these definitions, you can assign Workplace and Project roles with confidence, ensuring that each professional has access only to what is appropriate for their responsibilities – maintaining both security and efficiency in your workflows.
