Roles and access
The difference between built-in roles and your company's own roles, permissions by module and scope by desk and group.
On this page
In Settings → Roles and access you decide what each person can see and do. You can use the four built-in roles or create your company's own roles with finer permissions.
Built-in roles
They come ready in every company and cannot be changed or deleted. In the list they have the built-in tag:
Role | Permissions | Scope |
|---|---|---|
Administrator | Manage everything (users, roles, groups, SLA, catalog, workflows, email, audit log) | All desks |
Agent | Operate tickets, knowledge, workflows and the assistant; view the rest | All desks |
Viewer | View everything, without writing | All desks |
Requester | Portal only: their requests and approvals | Portal only |
Company roles
A company role, for example "Level 1" or "HR desk", defines two things:
Permissions by module
For each module you choose one of four levels:
No access: the module does not appear in the menu.
View: read-only.
Operate: also work on tickets and items, edit knowledge and complete tasks.
Administer: also create, change, delete and configure.
Modules are grouped like this:
Group | Modules |
|---|---|
Service desks | Incidents and requests, Problems, Changes, SLAs and calendars, Service catalog |
Agile and project desks | Agile boards, Project desks |
Knowledge and automation | Knowledge, Workflows and tasks, Elion assistant |
Analytics | Reports |
Administration | Desks, groups, rules, categories, services and organization; Settings (company, users, roles, email, integrations, audit) |
Scope
The scope decides which desks and which tickets the person sees:
All desks it can see: no restriction.
Only some: you choose some desks (or none, for all) and, within service desks, which tickets they see: those of certain resolver groups, those without a group and those assigned to or requested by the person. They see only the tickets that match something you checked.
The scope narrows tickets, problems, changes, agile and project desks, SLAs, reports and the assistant. In the matrix, those modules have the per scope tag when the scope is partial.
Private desks remain limited to their members, even with full scope. See Private desks.
What else counts
Besides their role in the company, each person has a role within each desk they are a member of (Viewer, Member, QA or Lead), and your company's plan decides which modules exist. A role does not open a module the plan does not include. See Roles and what each one sees.
Safeguards
There is always at least one active administrator in the company: a change that would leave zero is rejected.
Nobody can remove their own administration rights.
When you change a role's permissions, or a person's role, the sessions of those affected are closed so they sign in with their new access.
Every change is recorded in the Audit log.
Who can manage roles
Seeing the list and using View as requires at least View in the Settings module. Creating, editing and deleting roles requires Administer in that module.