 | Loading… |
|
|
|
Permissions
       
The Permissions tab allows you to manage user permissions.
The form can be accessed by clicking the individual user on the Users panel in Administration Panel and selecting the Security tab.
 |
HINT
To make it easier to check the settings of different users, you can open the form in a separate tab or window. Read more in the chapter Settings (Comparing permissions).
|
The form is made up of certain elements, which are described below.
In this section, you can filter and search by authorization tree or authorization name.
|
Permissions
|
If one or more checkboxes ( ) are checked, the program only displays the selected permissions in Permissions tree structure below.
Users can be assigned the following permissions:
- None – there are no permissions. The features is hidden from the user.
- Read – user can only read data.
- Write – user can read, write and change data.
- Delete – user can read, write, change and delete data. User has full permissions.
|
HINT
Each type of permission has its own icon.
|
|
| Granules type |
The filter allows the selection of one or more Granules assigned to the user. The current user authorizations and the default authorizations of the Granule are displayed. |
| Search |
The search engine searches the authorization tree, where the PANTHEON menu (authorization) names are written.
Confirm selection with the Enter key and all results are filtered and colored in yellow.
|
|
|
The location of current settings indicating the user (ACC_ANNE) and the authorization (APPL).
|
In this section, you can preview certain permissions for the user on the authorizations tree.
|
Datalab Applications
|
Displays the authorizations tree with Datalab Applications names (menu names).
The name is preceded by a permission icon, which can be set on the right side in the permissions management console.
Icons for permissions:
 – None  – Read  – Write  – Delete
|
|
APPL
|
Authorization (menu) name.
|
In this section, you can copy permissions from the source principal or propagate securities for the selected user.
|
(Source principal)
|
List of all principals (users) in database. From the drop-down list, select the user from which you want to copy the authorization settings.
|
|
Copy
|
Copies the authorization setting from the source principal to the selected user.
|
HINT
After clicking this button, a confirmation window is displayed to prevent the user from copying the rights unintentionally. The permissions are copied when the user clicks the OK button.
|
|
|
Apply changes
|
Applies all changes related to permissions.
|
|
|
- Propagate security – All child entities will adopt permissions as set on the parent entity. If child entities have inherited permissions, those permissions will not be affected.
- Propagate Security and Override Acquired – All child entities permissions will be affected and adopt permission as set on the parent entity.
- Propagate security explicitly – All child entities' permissions will be affected and adopt permission as set on the parent entity explicitly. Permissions on child entities that were previously inherited, will be explicitly set and no longer inherited.
|
HINT
Right click on the user permissons table enables the same propagate security functionality.
|
|
|
Propagate Security
|
Applies the selected propagate security from the drop-down list.
|
In this section, you can check and edit permissions for the selected user.
|
HINT
Right click on the user permissons table enables the propagate security functionality.
|
|
Name
|
User name for the user login.
The username is preceded by a permission icon, which can be set on the right side in the permissions management console.
|
|
Title
|
Name of the user.
|
|
Inherited from parent
|
Permissions are inherited from the parent entity.
|
|
Acquired from user group
|
If checked ( ), permissions are inherited from the user group when user is assigned (added) to the user group.
If not checked, permissions are set at the user level.
|
|
Basic permissions
|
- None – there are no permissions. The feature is hidden from the user.
- Read – user can only read data.
- Write – user can read, write and change data.
- Delete – user can read, write, change and delete data. User has full permissions.
|
HINT
Only one of these basic permissions can be selected.
|
|
|
Write period
|
Back for X days – used for authorizations for single documents. This parameter specifies for how many days in the past the user can change or delete documents.
Examples:
- 0 = the current day
- 1 = the current day and the day before
- 30 = thirty days back
- -1 = unlimited, documents can always be changed or deleted
|
HINT
When the write period is expired, the IRIS message is opened.
|
|
|
Full
|
If checked (), the user has full permissions (read, write, delete) for an indefinite period of time for the selected authorization.
|
|
Modified date
|
Date and time of the change.
|
|
Modified By
|
Username of the user who modified the data.
|
 |
Warning
- By default, the newly created user is without permissions.
- If the user is assigned to the user group, it inherits the permissions of the group.
- User can be a member of a group or not.
- If user is assigned to the group, the user inherits permissions of group.
- Permissions that are explicitly defined for the user will take priority over permissions set on a group.
- LT edition does not support authorizations, which means that you can assign the authorization only on the level of the entire program.
|
| Loading… |
| Loading… |
|
|
|
|