
How does conditional visibility work in Adalo?
Show or hide components based on user data, record values, inputs, dates, and other conditions—and debug the common gotchas.
Reviewed
Show the right component at the right moment using data and component state.
3 resources
Show or hide components based on user data, record values, inputs, dates, and other conditions—and debug the common gotchas.
Reviewed
Create a conditional toast, turn its state on after the main action, and use a short timer to reset the state and hide the message.
Reviewed
Show an image only on desktop by disabling its tablet and mobile visibility in the responsive Layout tab, then verify the parent group at every breakpoint.
Reviewed
Begin with the smallest record set that can demonstrate the intended result. Confirm the collection and property types, remove optional filters or conditions, and display one plain value from the current record. Once that basic path works, restore one rule at a time. The first rule that changes the expected result identifies the layer worth investigating.
Keep query logic, component visibility, and actions separate while debugging. A query decides which records are available. Visibility decides whether one interface element appears. An action changes data or navigation state. Treating those as different responsibilities makes it easier to explain both the successful path and the empty, denied, or missing-data states.
The resources above label their evidence and limitations individually. Use the reviewed date to judge freshness, follow current official sources for product behavior, and treat dated forum reports as examples of builder experience rather than guarantees. Finish with the testing checklist on the relevant page, including at least one record that should pass and one that should fail.
Tell us what should happen, what actually happens and where the two part ways.