Application vs project vs user roles

This page explains the different types of roles in Consult:

1. App-level roles: Assigned to each user and applied globally across the application, see Manage application roles.
2. Project-level roles: Assigned per project, currently only a project manager (PM), see Project roles.
3. Resource-level roles: Assigned per person, currently only a resource manager (RM).
4. Client-level roles: Assigned per client, currently only a client account lead (CAL).

These roles control what users can see and do in the application, on projects, and with other users.

App-level roles

App-level roles define broad capabilities across the entire Consult application. Typical app-level roles include:

• Administrator: Full access across the entire app.
• Employee: Partial access across the app, with more access given when project/resource/client roles are assigned to them.
• Consultant: Very limited access, with exceptions where project/resource/client roles are assigned to them.

Some actions explicitly bypass global admin rights. For example, approving schedules may require explicit approval.

Project-level roles (PM)

Project-level roles define what a user can do within a specific project. For most users, this will be limited to only seeing basic project information and being able to submit time for that project.

If a project administrator/director assigns the role of PM to a user (see Understanding the resources view), then that user will be PM with additional privileges, such as seeing the schedule or being able to create invoices.

At the moment, the only project-specific role on Consult is a PM.

Resource-level roles (RM)

Resource manager roles are scoped to an individual user (person) and gives access to that user's details. Individuals assigned to these roles are also required to perform managerial tasks such as approving time on projects and leave requests.

The following rights are given to the resource manager with regards to their direct reports:

• Access to report's profile page (excluding financial information).
• See report's leave types on the company calendar.
• See report's projects and edit hours across all projects.
• Approve timesheets and leave requests.

Resource managers operate across projects, unlike project managers who are scoped to a single project.

Client-level roles (CAL)

On the client level, a client account lead (CAL) can be configured that will have project manager access (including financials) of all projects belonging to a specific client.

::: warn These users will have access to sensitive financial information, such as project rates. Ensure you assign the right users before clicking save. ;::

How these roles interact

• Global override: App-level administrators usually bypass project-level restrictions unless explicit approval is required by a resource manager.
• Project vs resource roles: Project managers manage project-specific tasks and budgets; resource managers manage individual people across projects.

INFO

Although a user might have "Project Manager" as their Job Title or default rate card, this is not the same as a project manager assigned on project level. Therefore, this user would not automatically have project manager access to projects.