Roles are a set of permissions defined by the admin and mapped to users for managing their activities within the project. In addition to the predefined system roles (Project Administrator and Document Administrator), User can add custom roles by providing specific permissions, and further assigning this role to the users. We can create roles using two different methods.


Permission

Actions

Permission Management

View

  • This is the basic permission to create a role. Without view permission, a role cannot be created
  • With this permission, users can access Projects and its associated Teams 
  • The user should be assigned to a project to access the project
  • Users can access the Project Dashboard. Data displayed in the dashboard will be based on the Module Access permission. Users can also export the dashboard data in CSV/XLSX format

Create and Edit Teams

  • With this permission, users can create Teams
  • Users can edit the Teams created by them

Edit existing Teams

  • With this permission, users can edit the already existing Teams

Delete Teams

  • With this permission, users can delete the Teams

Archive Teams

  • With this permission, users can archive the Teams

Assign/Remove Users from Roles

  • With this permission, users can access the Project Users Tab in the inner side menu that displays the Assigned and Unassigned users with respect to the Role
  • If a user is assigned to Project Administrator Role, he or she will have permission to assign or remove fellow users from roles, except the Project Administrator role
  • If a user is assigned to a Custom Role (Roles created by Super Admin, Site Admin, and Hub Admin), with this permission user can assign fellow users to any role except for a Project Administrator & Document Administrator role

Assign Companies to Project 

  • With this permission, users can access the Companies menu within the project which will display all the Companies assigned to the Project. 
  • Users can also assign Companies to the Project and its Teams

Model Management

View

  • With this permission, users can access the Model Viewer and its associated tabs such as Model Directory, Hierarchy, Markups, and Property 
  • Users can view all the models in the Model Directory tab which are available in the Project and its associated Teams
  • Users can load the models in Viewer. All the viewer tools can be accessed
  • Users can view the properties of the element, including Custom Properties in the Property Tab
  • Users can upload IFC files from the local path
  • Users can export the models as IFC 4, IFC 4 Zip, IFC 2x3, and IFC 2x3 Zip
  • Users will have access to Plan View (Floor Plan/Drawing) of the Models
  • Users can load the Plan view in Viewer
  • Users can load the model with the desired “View”
  • The Hierarchy Tab shows the Hierarchy structure of the loaded model. The Hide, Isolate, Properties, and Custom Color options will be shown in each level of Hierarchy structure to inspect the Assembly/element on Viewer
  • The Markups Tab shows all the created 3D markups based on the loaded model. Users can create & delete the 3D Markups. All Markup Tools can be accessed
  • With this permission, users can the Models tab within the FILES menu that shows all the available models in the Project and its associated Teams
  • Within the Model Management, the “Load in Viewer” & “Import” options will be presented to load the model in the Viewer and to Import the IFC file from the local
  • Users can export the BOQ Report as CSV and PDF 

Create User based Views

  • With this permission, users can Create, Edit, and Delete the Saved Views.

Delete Models

  • With this permission, users can delete the models available in the Model Directory

View Iterations

  • With this permission, users can access the Iterations tab in the Model Viewer that shows all the iterations of the Model
  • User can compare two different model Iterations to track the element changes such as - Added, Modified, Not Modified, and Deleted

Model Transformation

  • With this permission, users can access to transfer into desired coordination of Models within the viewer 

Create Custom Property

  • With this permission, user can Create, Rename, and Delete the Custom Group and Custom Property in the Property Tab

Publish Model from Revit

  • With this permission, users can publish the Models from the Revit Application with help of Enginero Plug-In

Publish Model from SolidWorks

  • With this permission, users can publish the Models from the SolidWorks Application with help of Enginero Plug-In

Publish Model from Rhino

  • With this permission, users can publish the Models from the Rhino Application with help of Enginero Plug-In

Publish Model from Tekla

  • With this permission, users can publish the Models from the Tekla Application with help of Enginero Plug-In

Publish Model from SketchUp

  • With this permission, users can publish the Models from the SketchUp Application with help of Enginero Plug-In

Publish Model from Inventor

  • With this permission, users can publish the Models from the Inventor Application with help of Enginero Plug-In

Publish Model from Plant 3D

  • With this permission, users can publish the Models from the Plant 3D Application with help of Enginero Plug-In

Issue Management

View

  • With this permission, users can access Issue Management within the Project
  • With this permission, users can access the Issues tab in the Model Viewer where all the model-related issues can be viewed
  • Users can also access the Issues tab within the 2D Viewer where issues are viewed based on a loaded drawing sheet
  • Within the Issue Overview Page, users can view the issue details & its associated activities
  • Users can also Add & Remove the attachments
  • Users can export the Issues Report as CSV, PDF, and BCF

Create

  • With this permission, users can create Standalone Issue, Element Based Issue, Property Based Issue, Clash Based Issue, 2D Viewer Based Issue, and 3D Viewer Based Issue

Edit

  • With this permission, users can edit the issues

Delete

  • With this permission, users can delete the created Issues

Status Transition

  • By default, anyone with the Status Transition permission can change the status of an issue
  • Only users with the Status Transition permission can be assigned as a Status Owner in the Issue Workflow
  • If the Status Owner is enabled, by default Project Admin will be assigned as a Status Owner
  • Along with the Project Admin, anyone who is assigned as a Status Owner can be the only one who can change the status

RFI Management

View

  • With this permission, users can access the RFI Management within the Project
  • With this permission, users can access the RFI tab in the Model Viewer where all the model related RFI can be created
  • Users can also access the RFI tab within the 2D Viewer where RFI’s are created based on a loaded drawing sheet
  • In the RFI Overview Page, users can view the RFI details & its associated activities
  • Enables the users to be shown in the Distribution List field in the RFI Overview page
  • Users can also Add & Remove the attachments
  • Users can export the RFI’s Report as CSV and PDF

Create

  • With this permission, users can create Standalone RFI, Element Based RFI, Property Based RFI, Clash Based RFI, 2D Viewer Based RFI, and 3D Viewer Based RFI
  • Users can add fellow users to the Distribution list from the RFI Overview page

Edit

  • With this permission, users can edit the RFI Users can add/edit the fellow users in the Distribution list from the RFI Overview page
  • Users can add/edit their fellow users to the Distribution list from the RFI Overview page

Delete

  • With this permission, users can delete the created RFI’s

Status Transition

  • By default, anyone with the Status Transition permission can change the status of an RFI
  • Only users with the Status Transition permission can be assigned as a Status Owner in the RFI Workflow
  • If the Status Owner is enabled, by default Project Admin will be assigned as a Status Owner
  • Along with the Project Admin, anyone who is assigned as a Status Owner can be the only one who can change the status

Transform RFI as Issue

  • With this permission, user can transform RFI as an Issue in the RFI Overview Page

Document Management

View

  • With this permission, users can access the Document Management within the FILES where folders and files can be viewed
  • Enable the users to be listed in the Role/User selection dropdown within the Folder Detail page and in the share tab inside the file overview 
  • Based on the Folder Permission, users can view the files from assigned Projects (Project & Teams) which are maintained Globally under the main project
  • With the Read only Folder permission, users can view the Files, Folders, and its Sub Folder
  • With the Read and Write Folder permission, users can view the Files, Folders, and its Sub Folder. Users can also share the file to the fellow users and edit the file details

Create Folder

  • With the Read only Folder permission, users cannot create a folder
  • With the Read and Write Folder permission, users can create Folders and Sub Folders and provide fellow users permission to access the created folders

Upload Files

  • With the Read only Folder permission, users cannot upload the files
  • With the Read and Write Folder permission, users can upload the files from the local path. Users can also copy the files to another folder if both folders have Read and Write access

Delete

  • With the Read only Folder permission, users cannot Delete Folders or Files
  • With the Read and Write Folder permission, users can delete the Folders, Sub Folders and Files

Download

  • With the Read only Folder permission, users can download files to the local
  • With the Read and Write Folder permission, users can download files to the local

Administer Document

  • With this permission, users can act as a Document Administrator
  • Users can access all Folders and files in the Document Management and provide folder permission to the fellow users
  • With this permission, users can upload, delete, create, and copy, the folders and files

Status Transition

  • By default, anyone with the Status Transition permission can change the status of a document
  • Only user with the Status Transition permission can be assigned as a Status Owner in the Document Workflow
  • If the Status Owner is enabled, by default Project Admin and Document Admin will be assigned as a Status Owner
  • Along with the Project Admin and Document Admin, anyone who is assigned as a Status Owner can be the only one who can change the status

Drawing Management

View

  • With this permission, users can access the Drawing Management within the FILES where all the Drawing Sheets based on their assigned Projects are shown
  • Users can view the Drawing sheets in the 2D Viewer
  • Within the 2D Viewer, users can View, Create, Delete the 2D Markups that are relevant to the loaded drawing sheet. 
  • The Markup tools will be presented in 2D Viewer while creating/editing the 2D Markups

Upload

  • With this permission, users can upload the Drawing Sheets from the Local and publish from the Revit Application

Delete

  • With this permission, users can delete the Drawing sheets available in the Drawing Management

Download

  • With this permission, users can download the Drawing sheets to local

Asset Management

View

  • With this permission, users can access the Asset Management within the FILES where associated tabs such as Libraries, Categories, and Unassigned are shown
  • Users can view the Asset Overview page that provides a Mini Viewer to view assets, asset properties, Attachment, Libraries, and History
  • Within the Attachment tab, users can view, add, and delete the attachments
  • Within the Libraries tab, users can view the libraries assigned to an Asset and also, users can assign or remove the Libraries
  • History Tab – Not yet Implemented
  • With this permission, users can load the Project Assets in the Revit Application with help of Enginero Plug in

Edit

  • With this permission, users can edit the Published Asset in the Revit Application
  • With this permission, users can edit the Asset in the Revit Application which is published in the Asset Management inside the FILES tab

Publish

  • With this permission, users can publish the Assets in the Asset Management from the Revit Application with help of Enginero Plug in

Imports from Global Content

  • With this permission, users can import assets from the Global Content

Model Coordination

View Clashes

  • With this permission, users can access the Model Coordination tab within the project which provides access to its associated tabs such as Coordination Set, Clash Test, and Clash Result
  • Within the Coordination Set tab, users can view the Created Coordination Sets with the model information. Users can also export all the models available in the Coordination Set as an IFC file
  • Within the Clash Test Tab, users can view the Created Test names with the selected model details. Users can view the clashes related to the Test Name and selected Coordination Set by clicking on the View Result option
  • Within the Clash Result tab, users can view the clashes based on selected Coordination Set and Test Name
  • With this permission, users can access the Clashes tab inside the Model Viewer that shows clashes based on selected Coordination Set and Test Name
  • Within the Clashes tab, users can access the Pin, Group, Auto Group, and Ungroup options to use
  • Users can export the clashes Report as CSV, PDF, and HTML

Status Transition

  • By default, anyone with the Status Transition permission can change the status of a clash
  • Only user with the Status Transition permission can be assigned as a Status Owner in the Clashes Workflow
  • If the Status Owner is enabled, by default Project Admin will be assigned as a Status Owner
  • Along with the Project Admin, anyone who is assigned as a Status Owner can be the only one who can change the status 

Publish Clash from Navisworks

  • With this permission, users can publish the clashes from the Navisworks application with help of Enginero Plug-In 

Run Clashes

  • With this permission, users can run the clash test to detect the clashes between two selected models by clicking on Run Clash option

Create Coordination Set

  • With this permission, users can create the Coordination set in both Coordination Set tab and Clash Test tab
  • Users can also duplicate the created Coordination Set
  • With this permission, users can create, edit, and delete the Test Name in the Clash Test Tab
  • If the Model linked with Coordination Set is deleted from the Project, then the Coordination Set will also be deleted

Edit Coordination Set

  • With this permission, users can edit the existing Coordination Set

Delete Coordination Set

  • With this permission, users can delete the Coordination Set
  • If the Coordination Set is deleted, then its associated Test name and clashes will also be deleted

Role Permission for Project Role

Creating Roles using Admin Module

By default, the application will have a set of roles. Users can either duplicate those roles or create new roles. Follow the below steps to create a role,

  1. Select Admin > Global Roles module and click on the Create Role button (on Top Right)

Creating Roles using Admin Module

  1. Enter the Role Name and enable the permission for this role. After providing the details, click on the Create Role button to complete the process

Creating Roles using Admin Module (Cont.)

Creating Roles using Hub Module

All roles defined in the Global roles can be used in the Hub. Follow the below steps to create a role,

  1. Select Hub from the side Navigation and choose the desired Hub from the listed Hub

Creating Roles using Hub Module

  1. Select the Roles option and click on the Create Role button (on Top Right)

Creating Roles using Hub Module (Cont.)

  1. Enter the Role Name and enable the permission for this role. After providing the details, click on the Create Role button to complete the process

Creating Roles using Hub Module (Cont.)

Notes: 

    • The roles created in the Site will get carried over to all the available Hub whereas roles created within an Hub cannot be duplicated within the Site. The Hub Admin cannot edit the roles defined in the Site.

Created with the Personal Edition of HelpNDoc: Maximize Your Documentation Capabilities with a Help Authoring Tool