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.
| User Type | Description |
|---|---|
| 1. Administrator | Provides access to the complete Administration (System & Configuration) area of Cora PPM. Caution is advised in assigning this User Type, as most modifications made are system-wide and can impact input and collation of data. |
| 2. Full Application User | Provides full access to your instance of Cora PPM. Please note the level of access to features, functionality and projects is then controlled using permissions (See 4. Hierarchy View Permissions tab below), e.g., “Super Users” may have a full suite of Roles and Permissions across the complete Portfolio (or for their individual Programme/Department, etc.) |
| 3. Resource Only User | The user is restricted to the My Dashboard and Timesheets pages only. Users can see work that has been allocated to them in the My Dashboard, but cannot access projects or other areas of the system. Users can be assigned to Project Tasks and submit timesheets against those tasks. Resource Only users should not be given access to the Portal module. |
| 4. Portal Only | Users can only access the PORTAL (if purchased). They cannot access the main Cora PPM site. |
| 5. Inactive | Any user that is no longer using the system should be marked as inactive. Once made inactive they can no longer access the system and their licence is automatically freed up. It is not possible to delete users. This is to ensure an audit trail is maintained. |
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