DocumentaciónHelp

Space permissions

Restrict who gets into a knowledge space and with what level, by role, group or person.

On this page

By default, each person sees a space with the level their role gives them in Knowledge. With space permissions you can close it to a group of people, for example so that only the HR team can read and edit the People space.

Before you start

  • You need Manage in Knowledge (Administrator role).

How the rules work

  • With no custom rules, the space follows each role's level in Knowledge: the Viewer reads, the Agent edits and the Administrator manages.

  • With rules, only people who match a rule get in. For everyone else, the space doesn't exist: it doesn't appear in the list, in searches or in Elion's answers.

  • If a person matches several rules, the highest level applies.

  • A rule never exceeds the level the person has from their role. If you give a Viewer Edit in a space, they can still only read.

  • People with Manage in Knowledge keep Manage in all spaces, even if they don't appear in the rules. That way no one leaves a space without someone who can fix its permissions.

Each rule has a type, who it applies to and a level:

Type

Who it applies to

Built-in role

Everyone with that role: Administrators, Agents or Viewers.

Access role

People who have a role created by your company.

Group

The members of a resolver group.

Person

One specific person.

Level

What it allows in the space

Read

See published pages, search and see the history.

Edit

The above, plus create, edit, publish, move and archive pages, see drafts and comment.

Manage

The above, plus delete pages.

Since a rule never exceeds the role's level, and people who manage Knowledge already manage every space, in practice a Manage rule leaves the person with Edit. To delete pages you need Manage in Knowledge.

Space permissions govern what the team sees inside Elion ITSM. They don't change what requesters see in the portal or what help center visitors see: that's decided by the Spaces and visibility.

Steps

  1. Go into the space and press Permissions. Permissions for and the space name opens.

  2. If the space has no rules, you'll see No custom rules.

  3. Press Add. A new row appears.

  4. In the first list, choose the type: Built-in role, Access role, Group or Person.

  5. In the second, choose who it applies to:

    • for Built-in role, choose Administrators, Agents or Viewers;

    • for Group, choose the group from the list;

    • for Person, choose the person from the list (it shows their name and email);

    • for Access role, enter the role number (id) in Role id.

  6. In the third, choose the level: Read, Edit or Manage.

  7. Repeat from step 3 for each rule. To delete a row, press the trash icon (Remove row).

  8. Press Save.

You'll see Permissions saved. The changes apply right away.

If a row is missing who it applies to, you'll see a message like Choose a role, Group missing or Person missing, and nothing is saved until you fix it. If you repeat the same rule, it's saved only once, with the last level you chose.

As soon as you save the first rule, the space is closed to everyone else. If you only want to add someone, also add a rule for the others, for example Built-in role → Agents → Read.

Go back to permissions by role

  1. Go into the space and press Permissions.

  2. Delete all the rows with Remove row.

  3. Press Save.

The space goes back to following each role's level in Knowledge.

Example

To have only the RRHH group edit the Personas space and the rest of the team read it:

Type

Who

Level

Group

RRHH

Edit

Built-in role

Agents

Read

Built-in role

Viewers

Read

Related

Search Elion ITSM

Type at least 2 characters to search Elion ITSM.

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