Action Locks

In addition to rights on assignments, there is an option to lock certain actions, the so-called action locks. A User with system rights can block certain actions via the main menu images/download/thumbnails/299599526/Hauptmen%C3%BC_img.png in the "Settings" section under "Administration" by clicking on the link images/download/thumbnails/299599642/Action-locks_img.png .

Create an action lock

Define whether these actions should be blocked for all or a specific main group, group, type of identifier or identification code of an assignment. Each lock has the following settings:

  • Active: Check the box to activate the action lock.

  • Select the respective variant to be locked from the drop-down menu for Action, Type of identifier, Main group, Group and Identification code. For Action, Type of identifier, Main group, Group and Identification code always the one of the assignment that is checked is meant. All options must also apply, otherwise the action lock does not apply!

  • Creation login: The action lock applies to all assignments that were created with the specified creation login. It is important to note that all other information such as the group must also apply.

  • Administrator: Check this box and the lock is deactivated for the user with system rights.

  • Permit: A lock can be disabled by activating this checkbox. If, for example, you have locked all identification codes via the type of identifier, here you can allow an identification code again. It saves having to individually lock all the identifiers that need to be locked. It can also be used for groups.

  • Offset: In the offset row, if a lock refers to past assignments, you can specify for how many days in the past editing/deleting is not allowed. A positive value means, that the corresponding assignments in the past (in relation to the assignment end) can be deleted.

Set exceptions

For each action lock you can define exceptions for individual users or groups. Select the relevant line of the action lock and click on the images/download/thumbnails/299598659/2019-12-10_14h47_16.png -button in the "Exceptions" section.

Example: Holidays in the past are defined not to be changed. Via the exception, you can now authorise the "Administration" group to change them anyway.

You can set the exceptions for a main group and a group. In this case, the main group and the group of the logged-in user are checked. You can additionally select individual users for the exception rule to apply. Exceptions can be deactivated.