What are organisational structures?
The storage of passwords or documents ultimately always takes place according to defined organisational structures. The module enables arbitrarily complex structures to be defined, which later form the basis for the systematic storage of data. It is often possible to define them on the basis of already existing organigrams for the company or the department. Of course, it is also possible to use other criteria, such as the function / activity performed, as the basis for creating hierarchies. It is always up to the customer themselves to decide which structure is most useful for the purpose of the application.
Module-specific ribbon functions
The operation of the differs fundamentally in a couple of aspects to how it works in other modules. The following section will focus on only those elements of the ribbon that differ. The remaining actions have already be explained for the .
- New organisational unit/user: New organisational units or new users can be added via the ribbon, the keyboard shortcut “CTRL + N” or also the context menu that is accessed using the right mouse button. Due to its complexity, there is a separate section for this function: /
- Drag & Drop: If this option has been activated, it is possible to move users or organisational units in list view via drag & drop
- Permissions: The configuration of permissions within the organisational structure is important both for the administration of the structure and also as the basis for the permissions in accordance with . The benefits of “predefining rights” are explained in a .
- Settings: The settings can be configured for both users and also organisational units.
- Active Directory: The connection to Active Directory (available from the Enterprise Edition upwards) is explained in a
- Multifactor authentication: Additional security during login is provided through positive authentication based on another factor.
- Reset password: Administrators can reset the passwords with which users log in to Password Safe to a defined value. Naturally, this is only possible if the is configured via . In the alternative , the authentication is linked to the correct entry of the AD password.
The example below shows the configuration of a user where only the user themselves is a member.
This configuration means that the user password cannot be reset by administrators. The disadvantage is that if the password is lost there is no technical solution for “resetting” the password in the system.
Adding local organisational units
Both users and also organisational units themselves can be added as usual via the ribbon (alternatively via Ctrl + N or via the context menu). These processes are supported by various wizards. The example below shows the creation of a new organisational unit:
Create organisational unit
- Allocated organisational unit: If its defined here as the main organisational unit, the new object is not allocated to an existing organisational unit
- Rights template group: If an already existing organisational unit was selected under “allocated organisational unit”, you can select one of the existing here
When creating a new organisational unit, the second tab in the wizard enables you to directly create a new role. This role will not only be created but also given “read” rights to the newly created organisational unit.
The third tab of the wizard allows you to define the permissions for the newly created organisational unit. If an allocated organisational unit or a rights template group was defined in the first tab, the new organisational unit will inherit its permissions. Here, these permissions can be adapted if desired.