Organizational structure⚓︎

What are organizational structures?⚓︎

The storage of passwords or documents always takes place according to the defined organizational structures. The module enables 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 organization diagrams for the company or department. 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.

Relevant rights⚓︎

The following options are required for adding new organizational structures.

User rights⚓︎

• Can add new organizational units
• Display organizational structure module

Module-specific ribbon functions⚓︎

The operation of the ribbon 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 password module.

• New organizational unit/user: New organizational 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: New organizational structures / new users
• Drag & Drop: If this option has been activated, it is possible to move users or organizational units in list view via drag & drop
• Permissions: The configuration of permissions within the organizational structure is important both for the administration of the structure and also as the basis for the permissions in accordance with inheritance from organizational structures. The benefits of predefining rights are explained in a separate section.
• Settings: The settings can be configured for both users and also organizational units. More information on user settings…
• Active Directory: The connection to Active Directory (available from the Enterprise Edition upwards) is explained in a dedicated section
• Azure Active Directory: The connection to Azure Active Directory (available from the Enterprise Edition upwards) is explained in a dedicated section
• Multi Factor authentication: Additional security during login is provided through positive authentication based on another factor. More on this subject…
• Reset password: Administrators can reset the passwords with which users log in to Password Secure to a defined value. Naturally, this is only possible if the connection to Active Directory is configured via end-to-end encryption. In the alternative Master Key mode, 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 organizational units⚓︎

Both users and also organizational 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 organizational unit:

Create organizational unit⚓︎

• Allocated organizational unit: If the new object is defined as a main organizational unit, it is not allocated to an existing organizational unit
• Rights template group: If an already existing organizational unit was selected under "allocated organizational unit", you can select one of the existing rights template groups.

Create role⚓︎

When creating a new organizational 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 permission" to the newly created organizational unit.

Configuring rights⚓︎

The third tab of the wizard allows you to define the permissions for the newly created organizational unit. If an allocated organizational unit or a rights template group was defined in the first tab, the new organizational unit will inherit its permissions. These permissions can be adapted if desired.