Module Generator: Rights and visibility

Modified on Thu, 2 Apr at 4:20 PM

When configuring content blocks, you often need to restrict visibility and editability at the block level – while keeping the overall system open and accessible.

Scenarios for restrictions

Two typical cases are:

  • Many content blocks, different relevance: Depending on the workflow status, only some blocks are relevant. You can hide irrelevant blocks to keep the form clear for users.
  • Protect sensitive data: A form might contain confidential information that not all users should see or edit – for example, observations by the creator that should not be editable later.

Accessing the settings

Open the three-dot menu of a content block and select Configure rights and visibility.

Menu to configure rights and visibility

Visibility by status

When you restrict a block's visibility to specific statuses, it only appears in those statuses for all users. If you leave the field empty, the block appears in every status.

Use case: This lets you implement scenario 1 – hide irrelevant content and streamline the form.

Additional restriction to users

Once you've limited visibility to a status, you can further restrict it to users who have edit rights in that status. You define these users in the Workflow tab for the corresponding status.

Use case: This achieves part of scenario 2 – show sensitive data only to authorized users.

Read-only mode for statuses

Setting a block to Read-only for a specific status disables editing. The content is displayed but cannot be changed.

Use case: A block is filled in early statuses and appears as information in later statuses, but is not editable. This also addresses part of scenario 2 – making collected data immutable.

Exceptions with roles

You can define roles that bypass all restrictions and always see and edit the block. This is useful for roles like executive management that should have no restrictions.

Summary and best practice

Important: These block settings apply on top of the global rules in the Workflow tab and optional Access restrictions on the element (see Rights management). Configuration can quickly become complex. Use these settings sparingly to avoid unnecessary complexity.

Keep the following in mind:

  • Visibility by status: Show or hide blocks depending on the workflow phase.
  • Visibility for users: Only users with edit rights in that status see the block.
  • Read-only: Block is displayed but not editable.
  • Role exceptions: Specific roles bypass all restrictions.
##

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