Within BIM 360, roles are the means of indicating the member's job title within the project or organization, such as Architect, BIM Manager, or Project Manager. Roles can also be leveraged within the services and the two administration modules, Project Admin and Account Admin, to standardize permissions and workflow settings. They provide administrators with fine-grained control to ensure that each member has only the access they need to complete their assigned tasks.

Manage Roles in the Account Admin Module

Account administrators define a set of roles that will be available for an account and configure default module access for each role. The set of roles defined by adding desired custom roles and removing unwanted roles will be available for use for all your projects, both existing and new.

Depending on your company type, you may want to assign a different default access level to a role; for example, an architectural design company may need to grant broader access levels to the Architect role than a construction company.

  1. Click the Module Selector Account Admin .

  2. Click the Roles tab.

  3. Start entering a role to add, then click the role in the displayed drop-down list.

    Tip: If the role you searched for doesn't exist, you are prompted to create the role. Click the "Create [role]" field in the drop-down list.
  4. Click Add.

    Tip: The new role is added at the top of the list; however, when you refresh the page, the role appears in the alphabetical order in the list.
  5. Click in the columns to change access to each module as needed.

The changes made by account administrators on the Roles tab don't affect module access permissions of existing project members. For a change to take effect, the edited role needs to be assigned to a new or existing project member.

After the role is created, you can quickly assign folder permissions using the role. Refer to the Folder Permissions topic to learn more.

Note: Account administrators can only configure module access associated with project-level roles. Account-level roles, such as executives and account administrators, can't be edited. For example, members with an Executive role can access the Executive Overview dashboard in the Insight module, and this access is not configurable.

Remove a role

Removing a role from an account only restricts the availability of that role moving forward. It has no effect on the roles of existing project members, nor upon their access or permissions within the module. The removed role will not be available to assign to new members or be used in permission and workflow settings. Additionally, tasks previously assigned to a removed role or documents previously sent to a removed role will not be affected.

Note: If, as a project administrator you notice that you can't assign a role that used to exist to a new project member, this indicates that the role was removed by your account administrator.
  1. Click the Module Selector Account Admin .
  2. Click the Roles tab.
  3. Click next to a role to remove.

Refer to the table below for a few examples of how permissions associated with a given role can control access to modules, or read the Issue Permissions topic to learn more about default permission levels by role for issues.

img: No access img: Project member access img: Administrator access

Project Defaults Account Defaults
Project Admin Insight Document Management Project Management Cost Management Design Collaboration Model Coordination Field Management Account Admin Insight/Executive Overview
BIM Manager
Civil Engineer

Assign Roles in the Project Admin Module

When members are invited to a BIM 360 project, project administrators can assign them a role; this process automatically grants access to the module associated with the role defined on the Roles tab in the Account Admin module.

Project administrators can also manually edit a member’s permissions and module access. Permissions granted by project administrators succeed those specified by role. In this case, removing a member’s role doesn’t remove access to any modules they already had access to, or any permissions manually granted by an administrator. For example, the Executive role guarantees access to Insight and Project Home modules. However, removing that role doesn't affect the member's ability to access these two modules if that member had been granted administrator-level access before.

Granting someone Project Admin rights to the project automatically makes them an administrator for every Next Generation module they have access to. To learn more, see Manage Member Access.

A video showing how to use member roles to control access to different modules at the project-level is shown below: