Module Generator: Restrict rights

In Q.wiki modules, you can make content differently visible or editable for different users. These access rights and visibility settings can be configured at multiple levels – from the entire module down to individual content blocks.

Module visibility for roles

You can define which roles can see an entire module. If a module is not enabled for a role, it will not appear in the left navigation menu and is also not visible in the Q.wiki global search.

Access restrictions on individual elements

You can restrict access to a single element to specific users or groups. A colored button will then be displayed in the page header, indicating that this element is protected. When the restriction is disabled, all users can see the element.

Edit rights in the current workflow status

A user may see an element but cannot edit it in the current workflow status if the corresponding right is not set for their role. In this case, the Edit button is not available. Creating tasks or attachments is also not possible.

Transitions and workflow actions

Available transitions are filtered based on the current user role's rights. Users only see those transitions for which they have the necessary right to execute.

Read-only content blocks

You can mark individual content blocks as read-only for specific workflow statuses. The user will see the block but cannot edit its content. A lock icon next to the block heading indicates this state.

Hidden content blocks

Content blocks can be completely hidden from users if they either contain sensitive information or are not relevant in the current workflow status.