Skip to main content
Define User Roles and Access on a Project

This article explains how to define user roles, access levels and how to assign users to roles on a project.

Updated over a week ago

Pre-requisites:

Role privilege as mentioned below, on the project in which user roles and access are to be defined:

Below are the steps to define and manage user roles and access in a project:

1. In the 'Projects' area, navigate to the project where user roles and access are to be defined or managed.

2. Right-click on the required project. Select 'Roles & Users' then 'User Roles and Access'.

Alternately, mouse over the project thumbnail in the thumb view and click the icon. A layered page opens. Click 'User Roles and Access'.

2. It shows the existing project roles with the ability to create new roles and assign existing or new roles to users, organizations, and user groups.

3. To create a new project role, click the 'Create New Role' button which adds a new blank project role record.

4. Enter the project role name as required.

5. You can search for users from your organization by typing in their email address. Once found, press the 'Enter' key or select the user record that populates as a suggestion (at the bottom) to give them the corresponding permission on the project.

To assign existing users on the selected project to different roles, click or type in the

characters within the textbox and suggested names of user groups, organizations and users appear accordingly.

If you try to enter a role name already reserved by the system, (irrespective of the text format used) you will receive a prompt to rename the role. Below is the list of all system-reserved roles:

'RFI Controller', 'Tender Team Member', 'Tender Administrator', 'Workspace Administrator', 'Workspace - Administrator', 'Workspace Document Publisher', 'Workspace Member (View Only)', 'cBIM Publisher', 'cBIM Viewer', 'Field Administrator', 'Field Contractor', 'Field Inspector'

5. All the projects in Asite are enabled for the 'Field' module by default. Accordingly, the system creates three new 'Field' specific roles in all new projects - 'Field Administrator', 'Field Contractor', and 'Field Inspector'.

The 'Field Administrator' is an administrator for the site and performs admin activities for site forms. This user can raise site forms as well.​

The 'Field Contractor' is assigned site tasks identified and raised by the field inspector. The field contractor is expected to resolve them within a defined timeline. Once a defect is resolved, a field contractor is expected to assign a status as resolved to that field task.
The ​'Field Inspector' is expected to perform inspections, identify site issues, and raise them to the field contractor for resolution.

6. For any project which is BIM enabled upon creation or after creation, the system will create two new roles in such projects automatically - 'cBIM Publisher' and 'cBIM Viewer'

The 'cBIM Publisher' is a user who publishes the model files to Asite.​

The 'cBIM Viewer' is a user who views the model files uploaded by the 'cBIM Publisher' and does the required collaboration on those files.

7. Once you have selected user groups, organizations, or users against a role, selected users including the users in chosen user groups and organizations are assigned to the corresponding role.

8. Once a user is assigned to a role, you can mouse over their record and view the user's profile image, name, organization and email address.

9. Select the 'Instant Email Notify' checkbox to trigger an email notification to the new users regarding role assignment.

10. Click 'Save' to apply the changes.

  • Specifically while creating projects, there won't be any email triggered for role assignment to the user who created the project and has the 'Workspace Administrator' role. Any other role assignments after that will work based on the email notification settings.

11. You can search the roles from header search bars by role name or by entering the user's name, user group, or organization.

12. To remove user groups, organizations, or users from the role, click the icon against their title. A validation prompt will be displayed to confirm the removal.

13. Click on 'Continue' to confirm the removal of the selected organization, user group, or user from a particular role.


Check: FAQs


Did this answer your question?