Conditional Display
Conditional display lets parts of the interface appear or disappear depending on record values, roles, workflow state, or other project rules.
It helps keep screens focused by only showing information when it is relevant.
Display Rules
Record Values
Components can be shown or hidden based on values stored on the current record.
For example, a follow-up section might appear only when a record has the status "Needs follow-up". A set of fields might only appear when the project type is "External partner".
Workflow State
Conditional display can also follow workflow state.
For example, approval fields may appear only after a record has been submitted. Finance actions may appear only once a booking has been confirmed.
Permissions
Some interface elements may only appear for users with the right role or permission.
This can apply to tabs, rows, columns, fields, related-record areas, buttons, and other components.
Configuration Scope
Components
Conditional display applies to configured components.
This means it can be used for many different parts of the screen: input fields, content blocks, rows, columns, tabs, action buttons, related-record tables, cards, and portals.
Relationship to Components
The detailed behaviour of each component is covered in the Components section.
Conditional display describes when those components appear. The component documentation describes what each component does once it is visible.
Project Decisions
Project teams should clarify:
- which information should always be visible
- which information is only relevant sometimes
- which record values or workflow states should control visibility
- whether hiding information could confuse users
Example
A module for applications might show a "Rejection reason" field only when the application status is "Rejected".
The same module might show a "Send confirmation" button only when the status is "Approved" and the user has permission to send messages.
Design Goal
Conditional display should make screens simpler, not harder to understand.
If users cannot predict why something appears or disappears, the rule may need clearer wording, better grouping, or a different workflow design.