Overview
Visibility-based logic shows or hides an element or page based on whether another element is currently visible. It lets you chain logic: tie several elements to one parent so they all follow it, without re-entering the same condition on each.
Why this matters: When a whole group of elements should appear under the same circumstances, repeating the underlying condition on each one is fragile — change the rule and you have to update them all. Visibility-based logic lets you set the condition once on a parent element and have everything else simply follow its visibility, so the chain stays consistent.
How it works
Attach the logic to the dependent element or page and point it at the controlling element. The dependent element appears only when the controlling element is visible — and because the controlling element's own visibility may come from any other logic type, you can build chains where one root condition governs a whole branch.
Note: Only the controlling element's visibility is evaluated, not its answer. To branch on what was answered, use logic based on an answer instead.
Example
A page, "Water feature checks," is shown by a Location-property condition. Three follow-up elements — a photo, a reading, and a sign-off — each use visibility-based logic tied to that page. Set the property rule once on the page, and all three follow automatically; if the page is hidden at a dry Location, so are they.
Frequently asked questions
Q: Does this evaluate the controlling element's answer?
A: No — only whether it's currently visible. For answer-driven branching, use logic based on an answer.
Q: Can I chain several levels deep?
A: Yes. A dependent element can itself be the controlling element for others, so one root condition can govern a whole branch.
Q: How do I set it up?
A: Add logic to the dependent element or page and choose the "based on element visibility" condition. See Adding logic to a Checklist.