Everything you want to know about assigning Mail and Document Types to user roles.
In Aconex the user with the Project Admin role sets up all the other user roles at project level. With that done, they then assign the mail and document types each role is allowed use. The roles are then assigned to the organizations on your project. In this article we'll show you how it's done.
Creating roles breaks down into five steps, all of which are carried out as one process.
There’s a couple of things you need to think about before you start creating roles. No 1 is what roles does your project need? The second question is what types of mail and documents do these roles need to use for their work? Once you know the answers, you’ll be ready to start adding them. For more on roles, see Aconex user roles.
Aconex allows you to restrict what roles can see and select, which means they cannot accidentally use the wrong mail or doc type, even though other roles might be able to see them.
When adding roles you can select one to be the default role. This means the mail/doc types added to the default role will be available to a newly added organization without you having to set anything up.
Mail types can be, for example, RFIs, Site Instruction and transmittals.
See all the mail and doc types and statuses by selecting the Show All checkbox. Filter a long list by entering text into the field under Available… and above the list.
Document types can be drawings and contracts, for example.
Document statues are a way of showing what type of information a document contains. For example, the content could be a draft as opposed to a finished document.
Review Status Sets are groups of actions a user can use when reviewing a document type. For example, Approved, Rejected etc. One of these will already be added by default, but you can change the default to one set up by your organization. See Creating review status labels for your project for more information.
When you’ve carried out all three steps, click OK to finish creating the role. This is then saved to the list shown on the Mail/Documents Role Settings tab.
Yes, you have to assign your project’s roles to the organizations that have already joined the project so that they can use the project’s mail and doc types.
Assigning roles to an organization means you restrict an organization's access to both the roles and the mail and doc types those roles can access. This is very straightforward to do and should only take a few minutes, depending on the number of organizations there are.
That’s not a problem. You can fix this by selecting the Mail/Documents Role Settings tab clicking the role’s name. This opens the Create/Edit Role window where you can change any of the settings described above.