Introducing User Roles. As the Org Admin, you have responsibility for the users in your organization, and how they interact with Aconex.
As the org admin, you control how users in your organization interact with and access information on Aconex. You can create and disable their accounts, and manage permissions to give them access to functionality across different areas of the system.
Permissions are managed within User Roles, which are configured and assigned to each of your users.
When your organization first joined Aconex, it was given a default User Role set. However, we know each organization has different needs so we allow User Roles to be customized.
If a user in your organization receives a permission issue or is unable to access certain functionality, you’ll need to review the User Role(s) that have been assigned to them. Also see User role secured asset definitions.
Let's take a look at an example.
Only you (and your colleagues) have access to your organization's information. This applies to Oracle Support who are unable to alter permissions for your users - it's up to you as the admin to manage this.
Patrick, one of your colleagues has been asked to Upload a document. They follow the steps outlined in the support article but he cannot see the Upload a new document option. After contacting Oracle Support for help and they refer to the organization administrator (that's you), with some steps to Assign User Roles.
Let's take a look at Patrick's permissions in Aconex.
From Setup > User Role Assignment we’ll search for Patrick.
We can see he is assigned two User Roles. ‘Basic’ and ‘Basic+’.
This doesn’t tell us much about the specific permissions Patrick has access to, so let's click on User Role Configurations to view the permissions that are granted to these roles.
We can see the permission Upload new documents is set as 'N/A' for both roles. In fact, he doesn't seem to have many permissions in Documents, as many are set as N/A (or Not Applicable). How do Grant, Deny and N/A work?
You have at least three options to resolve this problem:
Permissions in Aconex are often called ‘Secured Assets’ or ‘Permission Assets’.
Notice the 'Document Admin' role has the required permission set to Grant, along with other permissions that Patrick may need access to.
Let’s go with option 2 and assign the 'Document Admin' role.
Click Assign User Roles to go back to the previous screen.
Tick the 'Document Admin' role and click Save.
Note: After you've changed a user's permissions, they may need to log out and log back in for the change to take effect.
Following option 1 would Grant permission to the Basic role and solve Patrick's issue, BUT we need to keep in mind this would also give permission for all users assigned the Basic role.
Patrick can now upload documents, restore historical versions and create transmittals.
You now know the basics of User Roles and permissions in Aconex, and are on your way to becoming an effective organization administrator!