Understanding Operations

Operations depend on:

  • The user and its role(s);

  • The scope, i.e. if it is part of a job, and if so, which job;

  • The type of operation, such as access, modification, creation, etc.;

  • The application element on which the action is performed, as well as its owner, container, and permission group(s); and

  • The permission rules that have been defined in the application.

From all but the last of these factors, the permission system determines a list of accesses that are required for the user on the target application element. For example, to rename a dashboard, a user must have ACCESS, MODIFY rights on said dashboard. For more details on the required accesses for operations on each type of application elements, please refer to Section Understanding Access Rights.

If the element is a scenario, the operation may involve a scenario lock. For more details, please refer to Section Understanding Scenario Locks.

Specific rights must be granted to the administrator(s) in charge of managing the permissions, which are themselves considered as a type of application element. For more details, please refer to Section Understanding Operations on Permissions.