Module Generator: Rights management

Modified on Thu, 2 Apr at 4:20 PM

In the Basis tab, you can configure the following permissions:

Module permissions – Restrict visibility

Basis tab with permission settings in Module Generator

You can restrict the visibility of an area to specific roles. This means the module in the left navigation bar and all content are only visible and accessible to the defined user group. Roles are configured in the Roles tab, specific to each module.

Important: If you assign a task to a user outside the defined permission group, for example, they will see the task on their personal page. However, they cannot access the module content.

Extend administration rights

You can expand administration rights for configuration by granting access to the configuration panel to users from the respective department, for example.

Rights for Key Users

Key Users have the right to edit the configuration. If the configuration has not yet been released, the right is set when you save next. For an already activated module, you must release the configuration so that new administrators gain access to the configuration panel.

Access restriction at element level

With access restriction, an editor can mark an element as access-restricted. This makes the element accessible only to the previously defined user group. When you activate this option, Configure access restriction appears:

Detailed configuration for access restriction

Configure users and groups

In the top field, you configure which users or groups should have access to the element.

You have the following options available:

  • Meta usersCreator and last editor
  • Roles – defined roles from the Roles tab
  • User selection fields – content from fields of type User selection

The creator is pre-selected. If you remove them and activate access restriction, the creator receives an error message when saving the element because they lack the necessary permissions to view the content they just edited.

Define label

In the Access restriction name field, you define the button label, for example "Treat as anonymous" or "Request with sensitive data".

Add tooltip

We recommend maintaining a tooltip to clarify the impact of the access restriction to users. Example: "When access restriction is activated, only the project manager, project team, and management have access to the project."

Activate by default

Access restriction can be activated by default. It will then be initially activated for every newly created element in the module.

Tip: Use this option with caution and only for highly sensitive module content.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article