Project role

A project role is what a person is on one project, Member or Project manager; for a client user it is also their elevation.

Written for
user, admin, integration-developer
Roles
member, project-manager, elevated-client-user
Requires
Feature
projects

A project role is a person's position on one project: Member or Project manager. Owners and Admins do not need one; they can do everything on every project. For a workspace Member, the project role is what turns a project they can list into a project they can work in. For a client user, being added to a project at all is their elevation: it widens what they see from "my own tickets" to "my client's tickets on this project".

How it relates to other concepts

  • The project role is the third factor of the capability formula: workspace role × client mode × project role.
  • A membership can carry a consultant category override that replaces the person's default category on time logged in this project.
  • Adding and removing members is recorded, and removal keeps the person's workspace access.

Rules

  • A full project member (a workspace user on the project) edits tickets, assigns them, comments at every audience, and logs time on the project's tickets.
  • A workspace-user Project manager may in addition edit the project's name and description, manage members and collaborating clients, elevate client users of any client on the project, set category overrides, and download the project's client timesheets. Only Owners and Admins change the billing client and billing mode.
  • A client user's elevation is usable only with a full login (password or passkey). Until then the members list shows "Elevated (needs a full login first)".
  • A client Project manager may elevate users of their own client only, and only when that client is the project's billing client or a collaborating client.
  • Elevated client users may be assigned tickets, and comment at Shared and Internal. They never log time, never set billing fields or estimates, and never see Staff comments.
  • Removing a project member ends their project role and, for a client user, the elevation. Workspace access is unchanged.

Example

Per is a workspace Member and Project manager on retail-shop. He adds a new consultant to the project and elevates Ola from Nordic Retail. He cannot change the project's billing client; he asks an Admin.

  • Manage project members Add workspace users to a project, elevate client users, change project roles, override the consultant category, and remove members.
  • Project manager What the Project manager role adds on one project, what still needs an Owner or Admin, and the limits when the manager is an elevated client user.
  • Workspace member What a Member does day to day in SAQ, with links to each task, and what a Member cannot do without the Owner or Admin role.
  • Client user What a client user sees and can do in SAQ, the difference between regular and elevated mode, and how a full login unlocks elevation.
  • Role What a person may do in SAQ follows from three things at once, their workspace role, their client mode, and their project role; this page gives the formula and points to the detailed role pages.