Administration Guide

Security Roles

On this page

A security role decides what its members may see and do. A role is a named set of permissions together with an access scope, and technician accounts are members of roles. What an account may do is the combination of the permissions of all its roles, each permission limited by the access scope of the role that grants it.

Roles only grant. No permission denies anything, and roles have no order or precedence among them. Adding a role to an account can only widen what the account may do. To take a permission away from an account, remove it from every role the account belongs to.

The checks run in the database each time records are listed or opened, so the record lists technicians work with in the Web App show only the records their roles allow.

Security roles apply to technician accounts. A direct connection to the database that does not identify itself is not limited by roles, which makes direct database access equivalent to full administrative access.

You administer roles in the Admin Center and in the Settings App. Both applications edit the same roles, and neither takes precedence over the other; see Admin Center and Settings App. The records a role reaches are set by its access scope; see Access Scope: Organizations and Workspaces. The individual permissions are listed in Permissions Reference.

How roles grant access

Object and administrative permissions

A role can carry two kinds of permissions:

  • Object permissions decide what an account may do to business records.
  • Administrative permissions decide which sections of the Settings App and the Admin Center an account may open.

The permissions are built into the product. You grant or withhold them in a role.

Besides the object classes, the permission tree groups general permissions under Management and Administration: Administrative Access (a node that is itself the Administrative Access permission, with Basic Administrative Access and the administrative permissions under it), Advanced Administrative Functions (such as Batch Update, Recurrent Ticket Management, the snippet permissions, and Add New Tags), Views and Boards Management, and Analytics and Dashboard Management. Each permission is described in Permissions Reference.

Object permissions

Which permissions an object class has is a property of the class, not a setting. Most classes have one of these shapes:

Shape Permissions Classes
Flat View, Modify, and Delete, each a single permission Contract, Purchase Order, SLA, Service, Location, Organization, Group, Person, Project, Vendor, Product, Stock Rule, Service Catalog Item, Library, Reservation, Approval Stage, Approval Request, Report
Owner-scoped Delete; View and Modify, each for any record or only for records you own Computer, Hardware, Tracked Software, Software License, Network, Document, Asset, Configuration, Consumable
Ticket-scoped Delete; View and Modify, each for any record, within your group, if you are the assignee, or if you are the requester Incident, Problem, Change Request, Work Order, Service Request
Assignee-scoped Delete; View and Modify, each with a permission for any record and one for records you are the assignee of, and no within-group or requester condition Project Task

A scoped permission reaches only the records that meet its condition. There is no separate Create permission, except for reports: creating a record outside a workflow action follows the class's Modify permission. Each class that supports activities also has a Manage Activities permission.

TIP: Have technicians change records through workflow actions, and grant the Modify permission only to administrators who understand the effect of editing records directly: Modify allows editing a record's form and creating records outside workflow actions. Brands, company addresses, and stock rooms have no Modify permission, so this advice does not apply to them: whoever maintains one of these lists needs its management permission, which covers every operation on the list. Grant Batch Update with the same care as the Modify permission.

The Settings App's permission tree shows only the classes your license covers: without the ITSM module the service desk classes are not in the tree, and without the ITAM module the asset classes are not. Permissions a role already holds for a class the tree hides stay stored until the role is next saved in the Settings App, which removes them. The Admin Center's permission tree is not limited by the license; see In the Admin Center.

How some permissions combine

  • Brand Management and Company Address Management, under Reference Tables, and Stock Room Management, under Asset Management > Stock Room, each let the account view, add, modify, and delete every entry of that list. Access scope does not narrow them.
  • Vendor products have no permissions of their own and follow the Product permissions. In the Web App, editing and deleting a vendor product both check the Product Modify permission.
  • Editing or deleting an approval stage or an approval request also needs the permission to edit the record being approved, when that record is found. Viewing a stage also needs the permission to view that record. A request is listed when the class of its record is visible to you; a request addressed to you is listed whatever the class of its record. See Approvals.
  • An activity can be edited or deleted only while you hold the class's Manage Activities permission, the record it belongs to is not open read-only, and the activity's category is not read-only. An activity whose category is not found counts as read-only.
  • In the Web App, Shared Snippets Management has an effect only together with Shared Snippets Use.
  • In the Customer Satisfaction Rating group, View All Ratings lets incident and service request lists show the requester's rating on every ticket, and View Own Ratings on the tickets you are the assignee of. Without them, those lists show the rating columns empty.
  • View All Articles reaches Knowledge Base articles in any status; the permission to view live articles reaches only articles in the Live status. Workspace scope applies to articles; organization scope does not.
  • Running reports is one permission, described as "Allows running reports". Which reports its holder sees in the report list follows the report: a report is listed for an account that holds, for any record, the View permission of a class the report is set up for, when the license also permits that permission. For Knowledge Base articles, that is the permission to view live articles; View All Articles does not count. A scoped View permission, such as View for tickets you are the assignee of, is not enough. A list report set up for no class is listed for every account.
  • Every account that belongs to at least one role can list announcements; no permission controls this, except in the Web App's Announcements list, which opens with no rows without Announcement Management.
  • The built-in service persons cannot be opened or edited by any account.

What technicians see in the Web App

  • Without a class's View permission, the class has no entry in the Web App's navigation, and a navigation group with no entries left is not shown. A scoped View permission is enough for the entry.
  • A few entries depend on other permissions: the boards need View on Work Orders, the team calendar needs View on Work Orders or on Project Tasks, recurrent tickets need Recurrent Ticket Management, printable reports need the permission to view reports and an application setting that does not turn reports off, and Analytics is always shown.
  • Some entries follow the View permission of other classes: All Tickets shows with View on Incidents, Problems, Change Requests, Work Orders, or Service Requests; All CIs with View on Computers, Hardware, Networks, Software Licenses, Documents, or Configurations; Software Products and Software Installations with View on Computers, Hardware, Tracked Software, or Software Licenses. My Tickets follows All Tickets, My Tasks follows Project Tasks, the Change Calendar follows Change Requests, and Discovered Installations follows Software Installations.
  • The navigation also follows the license: an entry that belongs only to a module your license does not include is not shown.
  • My Calendar offers only the classes you may view.
  • Editing a record's form needs the class's Modify permission: without it, the Web App shows the form's fields read-only.
  • The Actions menu of a grid's toolbar lists Batch Update for every technician, except on the pages that hide it; see Update Several Records at Once. Without the Batch Update permission, choosing it shows "You do not have enough permissions to use this function." On a dashboard's grid, choosing it always shows this message, even with the permission. With the permission, each selected record of a workflow class still needs the class's Modify permission: records it does not cover are skipped without an error, and the result reads "n out of m records have been successfully updated."
  • When some of a record's related records are outside your permissions, the Relationships tab lists only the related records you may view, without a message that others are hidden.

Administrative permissions

  • In the Settings App, Administrative Access satisfies every administrative permission check, except the business-logic permission of Invoice Items.
  • Basic Administrative Access is needed to sign in to the Settings App. Without it, the Settings App refuses with "You do not have enough permissions to use this function."; under automatic sign-in, it asks you to sign in again instead. The Import Wizard checks the same permission, unless it runs from the command line. The Web App checks it for access to the Admin Center.
  • Each node of the Settings App shows only to holders of its section's permission, and a parent node shows when one of its children does. A few nodes, such as Administrative Dashboard, show to everyone who can sign in. Opening a hidden node by other means shows "You do not have enough permissions to view this item." For General, Logs, and Services, holding the permission of any child section also grants the parent. Workflow and Business Logic is the exception: holding a permission under it does not grant the section itself, but the Workflow and Business Logic node and its category folders still show when a node under them shows.
  • Business logic permissions are granted per object class. Invoices and Invoice Items follow the Purchase Order class's business logic permission instead; see Permissions Reference.
  • Security Management is one permission that cannot be divided. In the Settings App it covers General > Workspaces, License Management, and Users & Security with everything under it: Accounts and Roles (Accounts, Roles, Applications), User Sessions, Password Policy, and SSO Providers. You cannot let an administrator manage accounts in the Settings App but not roles. In the Admin Center, the four pages of Users & Security (Accounts and Roles, Password Policy, User Sessions, SSO Providers) are all under Security Management, while the General > Workspaces page is under a permission of its own, not under Security Management. The Admin Center's menu, however, passes every permission check for an account that holds Administrative Access, so for such an account a page's own permission makes no difference to the menu.

Protection against locking yourself out

The database refuses a change that would make you, the technician making it, lose Basic Administrative Access, or lose both Administrative Access and Security Management. This covers removing yourself from a role and removing the permission from a role. Because the database enforces it, the rule applies in both applications and in the REST API. The error says that you can't remove yourself from the administrators' list, or from the security administrators' list.

Roles and members

  • Membership belongs to the account, not to the person, so a person with two accounts can be in different roles through each.
  • In the Settings App, a technician account keeps at least one role.
  • A role can be flagged as a default role. The Settings App's account wizard preselects default roles for a new account. The flag does not change what the role's members may do, and any number of roles can carry it.
  • Converting a technician account to a customer account in the Settings App removes it from all its roles when the account is saved; see Accounts.
  • A role also records which role-restricted workflow actions its members may run; see Workflow Overview.

What ships

Every new database starts with one security role, which holds Basic Administrative Access and Security Management, and one workspace, IT. The technician account you create together with the database is a member of this role.

A new 2026.1 database created with the Default Workflow also contains the roles and workspaces below; see Default Workflow Configuration. They are configuration that an administrator may change or delete, and a database upgraded from an earlier version need not have them.

  • Workspaces: IT, HR, Security, Facilities, and Shared.
  • Roles: Administrator (Full), Administrator (Log Management), Administrator (Security), Administrator (Services), Administrator (Views/Dashboards), Administrator (Workflow), Announcements Manager, Approval Manager, Asset Manager, Change Request Manager, Change Request Technician, Configuration Manager, Contact Manager, Group Manager, Knowledge Base Contributor, Knowledge Base Manager, Library Manager, Problem Manager, Problem Technician, Project Manager, Project Technician, Purchasing Manager, Report Designer, Report Viewer, Service Desk Manager, Service Desk Technician, Service Manager, Service Request Manager, Service Request Technician, Software Compliance Manager, and Viewer.

The role every new database starts with is named Administrator (Full) in the supplied configuration. There it also holds Administrative Access and is not restricted to workspaces, so the first technician account reaches every workspace.

No role of the supplied configuration is restricted to organizations. Every role except Administrator (Full) is restricted to the IT and Shared workspaces: through such a role, a member reaches no records in the HR, Security, or Facilities workspaces.

In the supplied configuration, Viewer is a default role, so the Settings App's account wizard preselects it for a new account. The operation of the supplied workflow that creates a technician account also adds the new account to every default role.

In the supplied configuration, the other administrator roles each hold part of the administrative permissions:

  • Administrator (Security): Basic Administrative Access, Security Management, and Browse Logs.
  • Administrator (Log Management): Basic Administrative Access and the permissions to browse and manage logs.
  • Administrator (Services): Basic Administrative Access, Browse Logs, and the permissions of sections under Services.
  • Administrator (Workflow): Basic Administrative Access, Browse Logs, the permissions of the Macros, Workflow Configuration, Configuration Parameters, Process Management, and Global Components sections, and the per-class business logic permissions.
  • Administrator (Views/Dashboards): Manage Shared Views and Boards, Manage Personal Views and Boards, Share Views and Boards, Manage Shared Dashboards and Charts, Manage Personal Dashboards and Charts, and Share Dashboards and Charts. It does not hold Basic Administrative Access, so a member who has no other role that grants it cannot sign in to the Settings App.

Each of these roles also holds both Export data permissions. Apart from the two Export data permissions, Viewer holds only view permissions, among them View All Articles and View Own Ratings but not View All Ratings.

When a role change takes effect

  • Record lists follow a role change at once.
  • Technicians who are signed in keep the administrative permissions and the account-wide permission checks they already loaded until their next sign-in. In the Settings App, saving a role you belong to, or any account, reloads your own Settings App permissions.
  • The Web App's navigation does not reflect a permission change immediately.
  • A change to snippet permissions reaches a technician in a new Web App session.

Instead of waiting for a signed-in technician's next sign-in, you can end the technician's session in the Settings App; see End a technician's session.

In the Settings App

To work with roles, you need Basic Administrative Access to sign in and Security Management or Administrative Access to see Users & Security.

Create or edit a role

  1. Go to Users & Security > Accounts and Roles > Roles. The list shows each role's Name, Description, Member Count, and Default.
  2. Click New to create a role. To change a role, double-click it, or select it and press Enter or click Edit. The New Security Role or Security Role [name] window opens.
  3. On the General tab, enter the Name and a Description. To make the role a default role, select This role will be assigned by default to all newly created Technician accounts; for a new role the box is clear.
  4. On the Permissions tab, grant permissions; see The permission tree.
  5. On the Members tab, add or remove members; see Add or remove members.
  6. On the Access Scope tab, set the workspaces and organizations; see Set the access scope.
  7. Click OK.

OK refuses an empty name and a name another role already has ("A role with name name already exists"). Changes on the Members tab and on the organization list are saved only when you click OK; Cancel discards them.

The role window's Workflow Actions tab lists the step actions and create actions allowed by the role, including actions open to every role.

The permission tree

  • Click in a node's Allow column, or press Space on the focused node, to tick or clear the node and every node under it. Ticking a class grants all its permissions. A parent whose children differ shows a grayed box.
  • A node in gray text is read-only and does not change with its parent. A node is shown this way when the ticket permission it maps to was already granted when the role was opened.
  • Ticking anything under Administrative Access also ticks Basic Administrative Access.
  • The right-click menu offers Expand All, Collapse All, Set, and Clear. Set and Clear tick or clear the selected rows and everything under them. Ctrl+A selects every row.
  • Right Arrow and Left Arrow expand and collapse the focused node. The bold group nodes, such as Service Desk and Asset Management, are always expanded; class nodes open collapsed.
  • The Description box under the tree shows the focused permission's description.

Add or remove members

  1. In the role window, open the Members tab.
  2. To add members, click Add. The Select Accounts dialog lists technician accounts. Select one or more and click OK. An account that is already a member is listed too; selecting it again adds nothing.
  3. To remove a member, select it, click Remove, and click Yes at "Are you sure you want to delete the selected item?". Only the membership is removed, not the account. Remove takes one member at a time.
  4. Click OK in the role window.

Add and Remove are also on the tab's right-click menu. A member cannot be opened from this tab.

If the role is the account's only role, Remove refuses with "The account cannot be removed as this is the only role assigned to it." and nothing changes.

Assign roles to an account

  1. Go to Users & Security > Accounts and Roles > Accounts and double-click the account, or select it and press Enter. The User Account [login] window opens.
  2. On the Member Of tab, which technician accounts have, click Add. The Select Roles dialog lists every role. Select one or more roles. A role the account already holds is listed too; selecting it again adds nothing.
  3. To take a role off the account, select it and click Remove.
  4. Click OK.

A technician account needs at least one role: OK refuses an account without one with "Technician accounts must have security roles. Please grant at least one role to this account."

Set the access scope

Access scope limits the records a role's permissions reach, by workspace and by organization; see Access Scope: Organizations and Workspaces. The Access Scope tab opens on its Workspaces sub-tab; Organizations is the second.

On Workspaces, the list shows every workspace, inactive ones included. Ticking All Workspaces ticks every workspace, and clearing any workspace clears All Workspaces. A role saved with every workspace ticked reaches all workspaces, including ones added later. A role that leaves at least one workspace unticked reaches a new workspace only after you tick it. OK refuses a role with no workspace ticked: "Include at least one workspace to the access scope of your security role."

To restrict the role to organizations:

  1. On Organizations, choose Restrict access to organizations. Under Unrestricted access, the list, its commands, and the check box are disabled.
  2. Click Add. The Select Organization dialog shows the organizations as a tree. Select one or more and click OK. Organizations already in the list are skipped.
  3. To include each member's own organization, select Allow access to objects within Current User's Organization. A role with this check box selected shows a <User's Organization> row in the list.
  4. To take organizations off the list, select one or more, click Remove, and click Yes. Removing the <User's Organization> row clears the check box.
  5. Click OK in the role window.

An organization in the list covers records of that organization only, not of its child organizations. If you restrict the role but list no organization, OK warns "You chose to restrict access to organizations but did not add any organizations. This role will prohibit access to any organization-related objects. Do you want to continue?" Yes saves a role whose permissions reach no record of a class that has an organization.

Copy a role

  1. On the Roles list, select the role and click Copy Item.
  2. In the Copy Role dialog, the Role Name is proposed as the role's name followed by " - Copy", or " - Copy (2)", " - Copy (3)", and so on when that name is taken or the role's name already ends that way. Change it if you like; it can be up to 50 characters.
  3. Click OK. OK trims leading and trailing spaces from the name and compares it with every role name, ignoring case; a taken name is refused with "Another role with this name already exists. Enter a different name."

The copy opens in the Security Role window. It has the source role's description, permissions, organization and workspace scope, and workflow action grants. It has no members, and it is not a default role.

Delete roles

  1. On the Roles list, select one or more roles and click Delete.
  2. At "Are you sure you want to delete the selected item?", or "Are you sure you want to delete n selected items?" for several roles, click Yes to confirm, or No to cancel before anything is deleted.

A role that has members is not deleted: "You cannot delete the "name" security role because it has members." When more selected roles remain, you are asked "Would you like to continue removing the remaining records?": Yes goes on with the next role, Yes to All goes on without further messages, and No stops. For the last selected role, the message has only OK. When you selected several roles and at least one was deleted, "n of m items have been deleted." reports how many went; when every selected role has members, nothing is deleted and no count is shown.

Deleting a role also deletes its permissions, its organization and workspace scope, and its workflow action grants.

Check a technician's effective permissions

  1. Go to Users & Security > Accounts and Roles > Accounts and open the technician account.
  2. Open the Effective Permissions tab. Technician accounts have this tab.

The tab shows the permission tree read-only, with an Allow and a Restricted column, and the commands Expand All and Collapse All. A permission is allowed when any of the account's roles grants it. It is marked Restricted when every role that grants it is restricted to organizations, or when every role that grants it lists an active workspace. For a restricted permission, the tab lists the workspaces and organizations that restrict it. A role that lists only inactive workspaces is shown unrestricted on this tab, although it still limits access to the workspaces it lists. Likewise, a permission granted by one role restricted only to organizations and by another role restricted only to workspaces is not marked Restricted, although each role's grant still reaches only the records inside that role's own scope.

If you changed the Member Of tab first, the Settings App asks "The record must be saved before proceeding with this action. Would you like to save the record now?" Yes saves the account; No stays on the current tab.

End a technician's session

  1. Go to Users & Security > User Sessions.
  2. In the Logged Users grid, select one or more sessions and click Terminate. The command is also on the right-click menu.
  3. Click Yes at "Are you sure you want to terminate the selected session?" or "Are you sure you want to terminate n selected sessions?".

In the Admin Center

The Admin Center's menu offers the Users & Security section to accounts that hold Security Management or Administrative Access. Its Accounts and Roles page has the tabs Accounts, Roles, and Applications. The Roles tab lists each role's Name, Description, Member Count, and Default (a check mark for a default role). Its toolbar has New, Edit, Copy, and Delete.

Create or edit a role

  1. Go to Users & Security > Accounts and Roles and open the Roles tab.
  2. Click New to create a role. To change a role, select exactly one role and click Edit; Edit is enabled only while one row is selected. The role opens with the tabs General, Permissions, Members, Workflow Actions, and Access Scope. A new role opens as New Security Role.
  3. On the General tab, enter the Name and, if you like, a Description. To make the role a default role, select This role will be assigned by default to all newly created Technician accounts.
  4. On the Permissions tab, grant permissions in the tree, which has the columns Name, Description, and Allow.
  5. On the Members tab, add or remove members, as described below.
  6. On Access Scope, set the scope on the Workspaces and Organizations sub-tabs, described below.
  7. Click Ok. One save stores the role together with its permissions, members, workspaces, and organizations.

Ok refuses an empty name with "The "Name" field is mandatory, it can't be left blank". A new role with a name another role already has is not saved either: an Error message reads "The server encountered an internal error and could not process your request. Please try again later or contact your administrator.", and the role stays open and is not created. Cancel is beside Ok.

The Permissions tab is not limited by your license: it lists the service desk and asset classes even when the Settings App hides them. It has no node for Invoice Management under Purchase Order, for Invoices under Business Logic Management, or for Dashboard Widgets.

Saving a role in the Admin Center replaces the role's stored permissions with the nodes ticked on the Permissions tab. A role that holds Invoice Management, Invoices under Business Logic Management, or Dashboard Widgets loses that permission the first time it is saved in the Admin Center. A role that holds Administrative Access opens with every permission under it ticked, so saving the role also stores those permissions.

The Workflow Actions tab is read-only. It lists, grouped by class, the step actions and create actions allowed to the role: the actions granted to the role and the actions open to any role. Its columns are ID, Kind, Name, and Enabled. Triggers are not listed. See Workflow Overview.

On Workspaces, the All Workspaces check box and the list of workspaces exclude each other. A new role starts with All Workspaces selected, and a role that is not restricted to workspaces shows it selected. Selecting All Workspaces clears every workspace selected in the list, and the list stays disabled while All Workspaces is selected. If All Workspaces is clear and no workspace is selected, saving the role is refused with "Include at least one workspace to the access scope of your security role."

On Organizations, choose Unrestricted access or Restricted access to organizations. Under restricted access, selecting Allow access to objects within Current User's Organization adds the first row, <User's Organization>, and clearing it removes the row. Remove also clears the check box when that first row is selected and at least one other organization is listed. Remove is disabled while no organization other than <User's Organization> is listed.

Add or remove members

On a role's Members tab, the list shows each member's Login, Person, Account Type, and Active.

  1. To add members, click Add. The Select Accounts panel lists technician accounts and has a search box. Select one or more accounts and click Ok. An account that is already a member is not added again.
  2. To remove members, select them, click Remove, and click Yes at "Are you sure you want to delete the selected item?". Remove is enabled only while at least one member is selected.
  3. Click Ok in the role. Membership changes are saved only then.

Remove on this tab does not check whether the role is the account's only role, so saving the role can leave a technician account without any role. The account's own Member Of tab, described below, does not save a technician account without a role.

Copy a role

Only the Roles tab offers Copy.

  1. On the Roles tab, select the role and click Copy.
  2. In the Copy Role window, the Name is proposed as the role's name followed by " - Copy". When other role names contain the source role's name, ignoring case, the proposal is " - Copy (n)", where n is the number of those other names. Change the name if you like.
  3. Click Ok.

The role is copied, and the new role opens on its General tab. It has the source role's description, permissions, workspace and organization scope, and workflow action grants. It has no members, and it is not a default role.

Delete roles

  1. On the Roles tab, select one or more roles and click Delete.
  2. At "Are you sure you want to delete the selected item?", or "Are you sure you want to delete n selected items?" for several roles, click Yes to confirm, or No to cancel.

A role that has members is not deleted: an Error message reads "You can't delete the "name" security role because it has members." with Ok and Help. When other selected roles can still be deleted, the message adds "Would you like to continue deleting the remaining records?" and offers Skip and Cancel instead of Ok. When several selected roles are all deleted, "n of n items have been deleted." confirms it.

Assign roles to an account

The account-creation wizard for a technician account has a step that assigns roles to the new account; see Create and Maintain Technician Accounts. If you continue from that step without a role, an error repeats the step's instructions and the wizard does not go on to its final step.

An existing technician account's roles are on the Member Of tab of the account. Saving a technician account that has no role is refused with "Technician accounts must have security roles. Please grant at least one role to this account." Ok in this message opens the account's Member Of tab; the message also offers Help.

Check a technician's effective permissions

  1. Go to Users & Security > Accounts and Roles and, on the Accounts tab, open the technician account. A technician account has the tabs General, Member Of, Effective Permissions, and Workflow Actions.
  2. Open the Effective Permissions tab.

The tab shows the account's effective permissions as a tree with the columns Name, Description, Allow, and Restricted. In Allow and Restricted, a check mark means that the row's own permission carries the mark. A row whose own permission does not carry it, but that has a row under it that does, shows a filled square instead. The same rule applies at every level of the tree.

A permission is marked Restricted when every role that grants it is restricted to organizations, or when every role that grants it lists an active workspace. A permission granted by one role restricted only to organizations and by another role restricted only to workspaces is not marked Restricted, although each role's grant still reaches only the records inside that role's own scope.

If you changed the Member Of tab and have not saved the account, clicking Effective Permissions asks "The record must be saved before proceeding with this action. Would you like to save the record now?" Yes saves the account without closing it and, when the save succeeds, opens Effective Permissions. No closes the question and leaves your unsaved changes in place.