Permissions

Relution allows permissions to be configured very precisely and in a fine-grained manner. This ensures that for each use case, a specific permission set can be created without giving users more functionality than necessary.

A permission can also enforce multi-factor authentication (MFA) for all users who have this permission. In addition, permissions can be made available to all organizations from the Global organization, and to all sub-organizations from a meta organization.


Overview of Permissions

Under Users → Permissions, default permissions are already available, e.g. Administrator, Teacher or Student. They apply globally to all organizations, correspond to the system groups and are linked to them. In the list, they are marked in the System column. These default permissions are managed automatically and cannot be modified, deleted or exported.

However, it is always possible to create new custom permissions.

Permissions are additive, meaning that all permissions assigned to a user account are combined.

Configuring Permissions

In the Permissions category, a new entry can be created by clicking Add. The Name is mandatory (up to 255 characters); a Description (up to 4000 characters) is optional. Almost every function available in the Relution Portal can be assigned individually.

Typically, there are four options: Read, Create, Update, and Delete. If an option requires another one, the required option is enabled automatically and locked, e.g. Create requires Read.

For example, a user can be given an account with read-only permissions, preventing them from making changes to the system.

Device actions can also be configured individually.

  • Example: All actions are allowed except for device location tracking.
  • Another use case: A user may only renew the tokens for Apps and Books (VPP in the portal) and Automated Device Enrollment (ADE, DEP in the portal) but not make any other changes. For Apps and Books, this requires the Update option in the Volume Purchase Programm (VPP) entry; for ADE, the Create option in the Apple Automated Device Enrollment entry. There is no Update option for ADE; with Create, the user can also add new ADE server accounts.

Enforcing Multi-Factor Authentication

With the Enforce multi-factor authentication for the role option, all users with this permission must sign in using MFA. The Multi-factor authentication section only appears if at least one MFA method is enabled under Settings → Login Management. Since the default permissions cannot be modified, a custom permission is required for this. Details can be found in the article Multi-factor authentication →.


Scope

The Scope column shows where a permission applies: Local (only in the own organization), Meta (in all sub-organizations of a meta organization) or Global (in all organizations). New permissions are created locally.

In the Global organization, the context menu entry Set visibility to global makes selected permissions available in all organizations; in a meta organization, Set visibility to meta makes them available in all sub-organizations. This does not assign the permission to anyone; it only becomes available for selection there.


Exporting and Importing Permissions

Via the context menu of the list, selected permissions can be saved as a JSON file with Export permissions and read in again with Import permissions, e.g. in another organization. Imported permissions are always created locally. Default permissions cannot be exported.


Linking Permissions to User Accounts

In the user account, a permission is assigned in the Direct Memberships area under Groups & Permissions: the Manage Permissions button in the Permissions field opens the selection.

Permissions can also be assigned to a group in the same way. All members of the group then receive them, including via nested groups.


Assigning Permissions During CSV Import

Permissions can also be assigned when creating multiple user accounts through the CSV import. The import process itself is described in CSV Import →.

The assignment can be done in three ways:

  • In the permissions column of the CSV template, permissions are entered per row using their exact name, e.g. Teacher or Student. Multiple entries are separated by |.
  • In the memberOfGroups column, groups are entered using their exact name, e.g. the system group [Organization] Teacher. The user account receives the group’s permissions through the group membership.
  • In the optional Groups step of the import dialog, one or more existing groups are selected. All imported user accounts become members of these groups in addition to the groups from memberOfGroups. This step is only visible with read permission on groups.

An unknown name in permissions causes the affected row not to be imported. The same applies to memberOfGroups unless the Automatically create groups and classes option is enabled; with this option, a new, empty group without permissions is created.

The names of the system groups include the unique name of the respective organization, e.g. [Organization] Teacher or [Organization] Student. The corresponding default permissions are named without this prefix, e.g. Teacher or Student.

How helpful was this article?