1. Help
  2. Getting Started
  3. Roles Overview
  1. Help
  2. Getting Started
  3. Roles Overview
purple icon for coordination.
We’ve moved!
Our Help Center has a new home and our URLs have changed. Please update your bookmark to this page before April 30, 2026

Roles Overview

The 17 account roles and 4 directory account roles, what each is for, and how they build on the Specialist foundation.

Roles decide what a person can see and do in an account. A person can hold several roles at once, and through account trusts, even roles in other accounts. This page is the who-does-what map. A person's roles live on their person record, in the Roles & Teams section.

Account roles

RoleWhat it is for
End UserUses services through self service. No specialist access.
Key ContactAn end user who also acts as a contact point for their organization.
AuditorRead access for reviewing account activity.
Financial ManagerManages the account's financial data.
SpecialistThe foundation role for working on assignments. Most other roles build on it.
Service Desk AnalystFront line. Registers and handles requests, including on behalf of others.
Service Desk ManagerOversees service desk operations.
Knowledge ManagerMaintains the knowledge base.
Problem ManagerRoot cause analysis and problem resolution.
Workflow ManagerDesigns and manages workflows, which is how Xurrent executes change.
Workflow RequestorRaises workflows from approved workflow templates and fills them in, without managing them. See Workflow Requestor below.
Release ManagerCoordinates releases.
Project ManagerPlans and runs projects.
Service Level ManagerManages services, offerings, and SLAs.
Configuration ManagerMaintains the CMDB and asset data.
Account DesignerCustomizes the account's configuration, including UI extensions and designs.
Account AdministratorFull administrative control of the account, including trusts.

Rule of thumb: the Specialist role is the prerequisite foundation for the manager level roles above it.

Workflow Requestor

The Workflow Requestor role lets a person raise a change without becoming its Workflow Manager. It requires the Specialist role, which gives read access to the account's workflows.

  • Raise: a Workflow Requestor can create a workflow from a workflow template that names a Workflow Manager (or whose service has a Change Manager) and that does not repeat on a schedule.
  • Manager: the workflow's Manager is taken from the template. The Workflow Requestor cannot choose or change it, and is never the Manager of the workflows they raise.
  • Before the workflow starts: the Workflow Requestor can edit the workflows they raised and start them. They cannot change the status, completion reason, phases, task dependencies, template, manager, linked problems, or invoices.
  • After the workflow starts: the Workflow Requestor can only add notes, update custom fields, and link requests.
  • After the workflow is completed: it is read-only to the Workflow Requestor.
  • Out of scope: the role gives no write access to workflows raised by other people, and cannot duplicate a workflow. Workflows created automatically from a request template or a recurring schedule are not owned by any Workflow Requestor.

Directory account roles

In organizations with a directory account, four roles govern the shared directory.

RoleWhat it is for
Directory AuditorRead access for reviewing directory data.
Financial ManagerFinancial oversight at directory level.
Directory DesignerConfigures the directory account's setup.
Directory AdministratorFull administrative control of the directory account.

Related

See Account Trust for roles that span accounts, and Person for where roles are assigned.