Managing User Roles

Overview

The role concept ensures that users of the INUBIT software are only able to display and modify those functions and rights they are authorized for.

A user role is a collection of rights and may be freely configured. The rights grant users access to certain functions of the INUBIT Workbench and access to certain data objects.

Overview about "right/role" assignments

You can find an overview about all roles and their rights in the INUBIT Workbench in the Administration > User Roles tab.

Pre-configured roles

The INUBIT software contains some pre-configured roles. You can use and adjust them or add further roles and configure them freely. The following roles are included in the scope of delivery:

System Administrator

This role manages and maintains the system in the operational field. This role owns all available rights. The right assignments cannot be changed.
Project Lead

This role leads and manages a project. The role has rights similar to the system administrator. Some rights for technical monitoring (access to the Audit Log, the Connection Manager, and the Process Data Logger), the option to create application and diagram profiles, and the access to the metadata and plug-in manager are missing.
SOA Developer

This role transposes business models into Technical Workflows and can access all diagram types because these are needed for generating and linking. This role has rights similar to the project lead, but without configuration rights, without the right to use the su mode, and has only restricted access to modules and system connectors as well as access to process maps and BPDs.
Business Analyst

This role creates and maintains business models. Thus, the role can access all non-technical diagram types as, for example, Business Process Diagrams, and Organizational Diagrams. Additionally, a Business Analyst can create BPM rules, use the Repository, versioning (only create tags), and the Report Generator for creating reports.
EAI Developer

This role integrates third-party systems via Technical Workflows. Unlike the SOA developer, the EAI developer can access all modules and system connectors as well as process maps and BPDs.

When a user has the permission to Edit in INUBIT Workbench > Administration > User Roles > Rights of user role > Designer and INUBIT Workbench > Administration > User Roles > Rights of user role > Module Editor in a version lower than INUBIT 7.4 and this user is being migrated to INUBIT 8.1, then the user will be automatically given permissions in INUBIT 8.1 to Create, Edit, and Delete in INUBIT Workbench > Administration > User Roles > Rights of user role > Designer and INUBIT Workbench > Administration > User Roles > Rights of user role > Module Editor for his respective group or higher-level group. Revoking any of these permissions after the migration must be done manually in INUBIT 8.1.

Creating and Configuring Roles

Proceed as follows

In the INUBIT Workbench, display the Administration > User Roles tab.
Select a role.
Open the context menu and choose New User Role. A dialog opens.
Enter the name of the new user role.
Click OK to close the dialog.

The new user role is sorted alphabetically in the tree structure and displayed. In the right area there is a summary of all rights that may be assigned to the role.

Select all the rights that are to be allocated to the new user role.

If working in teams, it is important that the team members be able to assign the diagrams and modules to the group or higher-level group directory.

If diagrams and modules are only assigned to their own particular user directory, the other group members will not be able to see them and/or develop them further.

To assign a new user role to a team member, activate the rights for Designer and Module Editor that contain groups and superordinate groups.

To save, click .

→ Now, you can assign the role to users.

Deleting User Roles

User roles can only be deleted if no more users have been allocated to the role.

Proceed as follows

In INUBIT Workbench display the Administration > User Roles tab.
Select the role to be deleted.

Open the context menu and choose Delete User Role.

If the Clear repository files checkbox is selected, then the old versions of the repository files created by the user will be deleted.

If the base version is 1, then a new version will be created with all the tags and the username is changed to “Deleted User”.

If a version has any active tags, then that version will have no effect.

If the checkbox is not selected, the repository files will not be deleted.

Confirm the prompt with OK.

→ The role is deleted and no longer displayed in the User Roles tab.