DocumentaciónHelp

Create a custom role

Create a role for your company with permissions by module and a scope limited to certain desks, groups or tickets.

On this page

Create a custom role when the built-in roles do not fit: for example, a level 1 agent who only works on their groups' tickets, or a development team that only uses agile desks.

Before you start

  • You need Administer in the Settings module (for example, the Administrator role).

  • If you are going to limit the scope to certain groups, create them first in Create a resolver group.

Steps

  1. Go to Settings → Roles and access.

  2. Click New role.

  3. If you want to start from a base, choose a Template. It fills in the permissions and scope, which you can adjust later:

    • Blank: everything set to No access.

    • Level 1 agent (their groups): operates tickets, knowledge, workflows and the assistant; views the catalog and SLAs; scope limited to tickets without a group and their own. Then check the person's groups in Scope.

    • Supervisor (read-only everywhere): views everything, without writing, and does not enter Settings.

    • Development team (agile desks): operates agile desks and the assistant, and views knowledge.

  4. Enter the Name (up to 60 characters) and, if you want, a Description.

  5. In Permissions by module, choose No access, View, Operate or Administer for each module.

  6. In Scope, choose:

    • All desks it can see, or

    • Only some, and then:

      • In Desks (none checked = all), check the desks they will see. If you check none, they see all.

      • In Within a service desk, tickets from, check the groups whose tickets they will see (Group name), Those without a group and Those assigned to or requested by the person.

  7. If you want to review the result, click View as this role. See View as this role.

  8. Click Save.

You see the message "Role “Name” created: assign it to users from “Edit”." and the role appears in the list.

With Only some you must check at least something: desks, groups, Those without a group or Those assigned to or requested by the person. Otherwise, Elion ITSM asks you to Choose the scope: all desks, some desks, groups, those without a group, or their own.

If something fails

  • That name belongs to a built-in role: choose another.: you cannot name your role Administrator, Agent, Viewer or Requester.

  • A role with that name already exists.: use another name.

Assign the role to people

A new role has no users. To assign it:

With Only some, within service desks the person sees only the tickets you checked: those of the chosen groups, those without a group (if you check Those without a group) and their own (if you check Those assigned to or requested by the person). If you check no group, in service desks they will see only their own tickets. This group restriction does not apply to agile or project desks.

An example for an HR desk: choose Only some, check the HR desk in Desks, check all the groups in that desk and check Those without a group. The person will see only that desk and all its tickets.

Related

Search Elion ITSM

Type at least 2 characters to search Elion ITSM.

↑↓ to navigate · Enter to open · Esc to close