Cora, through configuration, provides several security and access features available to administrators so that all users are not daunted with the many features available in Cora. Furthermore, Cora provides the administrators with a level of comfort that users cannot make changes to either the configuration or the data by accident.
System access and data access is a vital step in the implementation of Cora and it is important to avoid giving users access to change system settings that affect other users. It is also just as important to make sure users are not being given access to projects and data that they don’t need to have access to. This means giving each user access to only the project(s) that they need to see, and then, defining which of the project(s) they actually update on those projects that they see.
There are three key components of Cora that drive this, the user type as in license type, the system role assigned to the user, and then group access (or Project Access and matching Project Profile). Note that there are further access settings available to administrators to add further granularity, however this article will focus on user types.
User types are based on the quantity of Cora licences owned by your organisation. Meaning, the licence/ user type is linked to the available licences owned of Cora, therefore deciding on what user type to assign to a user is very important as these are usually limited in quantity.
Items 1 and 2 below are FULL USER types, 3 and 4 are RESTRICTED USER TYPES and item 5 below frees up a licence for someone else to use. A FULL USER allows access to all parts of the Cora front end and Mobile Device, where a RESTRICTED USER will not have access to the full system, only to the parts that it describes. Please contact your Cora representative for further details.
Every user MUST be assigned one of the 5 user types, and can ONLY have one user type at any one given time.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article