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 are how you will manage most of your organization's permissions in Aconex.
These permission settings apply to:
Keep in mind, project-level Grant or Deny settings can change organization-level permissions for a specific project, unless the organization-level setting is Deny. We'll explain in the next section.
| Setting option | What it does |
|---|---|
| Grant | Gives permission to this function. |
| Deny | Prevents 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/A | N/A can be overridden by another user role. N/A is assigned by default. And by default, N/A does not grant permission to the function, so it can be considered 'not assigned'. |
User roles for your organization apply to every project your organization is involved with.
If you need to change a user’s permissions for one specific project, create a user role at the project-level.
Project-level Grant or Deny settings can override organization-level settings for a specific project. However, an organization-level Deny cannot be overridden.
Project-level N/A means no permission is assigned at the project level, so the organization-level setting still applies unless another role grants or denies access.
| Setting option | What it does |
|---|---|
| Grant | Gives permission to anyone in your organization for this project. Overrides any setting at the organization-level. But only for this project. |
| Deny | Denies 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/A | This setting can be modified by another user role. N/A is assigned by default. And by default, N/A does not grant permission to the function, so it can be considered 'not assigned'. |
Why would I create a user role at the project-level?
Create a new user role at the project-level (these instructions also show you how to delete user roles)
See the table below for each possible settings combination, and the outcome for your project.
| Organization-level setting | Project-level setting | Then the result for the project is |
|---|---|---|
| Deny | Grant | Deny |
| N/A | Grant | Grant |
| Grant | Deny | Deny |
| Grant | N/A | Grant |
| N/A | N/A | Deny |
| N/A | Deny | Deny |
| Grant | Grant | Grant |
| Deny | Deny | Deny |
| Deny | N/A | Deny |