You are here

Manage user roles for your organization

As the Org Admin, you can create and modify user roles for people in your organization. There are two types of user roles you'll be managing - organization-level user roles and project-level user roles.

Organization-level user roles

Organization-level user roles are how you will manage most of your organization's permissions in Aconex.

These permission settings apply to: 

  • everyone in your organization,
  • who has been assigned this user role
  • for every project they are working on.

Keep in mind, these settings can be overriden by project-level user roles for specific projects. We'll explain in the next section.

Setting optionWhat it does
GrantGives permission to this function.
DenyPrevents access to this function. This setting cannot be overridden by a project-level user role. Also, if a user has a number of roles, and Deny is set for one of them, that will prevent them from using the functionality even if it's enabled for another role that's applied to them. In most cases, we recommend using N/A instead.
N/AN/A can be overridden by another user role. N/A is assigned by default. And by default, N/A will deny permission to the function.
org roles across projects

Project-level user roles

If you need to change a user’s permissions for one specific project, create a user role at the project-level.

Project-level user role settings will override any organization-level settings except the Deny setting, but only overrides them for the specific project.

The only time project-level user role settings do not override organization-level user roles is when the org-level role setting is set to deny.

Setting optionWhat it does
GrantGives permission to anyone in your organization for this project. Overrides any setting at the organization-level. But only for this project.
DenyDenies access to anyone in your organization for this project. Overrides any setting at the organization-level except the Deny setting, but only overrides them for this project.
N/AThis setting can be modified by another user role. N/A is assigned by default. And by default, N/A will deny permission to the setting.

More information about project-level user roles

How do Grant, Deny and N/A work?

See the table below for each possible settings combination, and the outcome for your project.

Organization-level settingProject-level settingThen the result for the project is
DenyGrantDeny
N/AGrantGrant
GrantDenyDeny
GrantN/AGrant
N/AN/ADeny
N/ADenyDeny
GrantGrantGrant
DenyDenyDeny
DenyN/ADeny

Feedback