> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/docs/platform/extensibility/experience-builder/control-element-visibility/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# Control element visibility

> Control whether elements are shown or hidden in Experience Builder using static or dynamic visibility settings to create interactive, personalized experiences.

Control whether elements are shown or hidden in Experience Builder using static or dynamic visibility settings to create interactive, personalized experiences.

Visibility controls whether an element is displayed in your experience. In Experience Builder, you can show or hide elements using static settings or dynamic conditions based on application state, user interactions, or data. This enables you to create interactive experiences that display only the content that is relevant to users.

## Benefits of visibility controls

Use visibility controls to:

* Show or hide content based on user interactions.
* Display content only when specific conditions are met.
* Create dynamic and personalized user experiences.
* Simplify page layouts by displaying content only when needed.
* Improve usability by reducing visual clutter.

## Visibility options

Experience Builder supports two types of visibility controls:

Static visibility

Use static visibility to permanently show or hide an element regardless of user interactions or application state. For example, you can hide an element that is still under development or temporarily disable content without deleting it.

Dynamic visibility

Use dynamic visibility to display or hide elements based on conditions such as:

* User interactions
* Component or page state
* Form values
* Data returned from an integration
* Expressions or conditional logic

Dynamic visibility is commonly used to build interactive user interfaces that respond to user actions.

> Control whether elements are shown or hidden in Experience Builder using static or dynamic visibility settings to create interactive, personalized experiences.

## Docs

- [Configure element visibility](https://zuora.ferndocs.com/docs/platform/extensibility/experience-builder/control-element-visibility/configure-element-visibility.md): Learn how to configure whether an element is displayed, hidden, or shown based on a dynamic visibility condition in Experience Builder.
- [Create a dynamic visibility condition](https://zuora.ferndocs.com/docs/platform/extensibility/experience-builder/control-element-visibility/create-a-dynamic-visibility-condition.md): Learn how to configure dynamic visibility so an element shows or hides automatically based on a condition.
- [Common use cases](https://zuora.ferndocs.com/docs/platform/extensibility/experience-builder/control-element-visibility/common-use-cases.md): Common use cases for visibility controls, including showing messages, revealing fields, managing dialogs, and displaying content based on user actions or permissions.
- [Visibility versus conditional rendering](https://zuora.ferndocs.com/docs/platform/extensibility/experience-builder/control-element-visibility/visibility-versus-conditional-rendering.md): When to use visibility versus conditional rendering to hide, show, or conditionally include elements in an experience.
- [Best practices](https://zuora.ferndocs.com/docs/platform/extensibility/experience-builder/control-element-visibility/best-practices.md): Use visibility controls and dynamic visibility to create responsive, interactive experiences with clear conditions and thorough testing.