> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/customize-app/component-visibility.md).

# Component Visibility

In some forms, you may want to show an input or view component based on the data entered in another input. Here is an example of how you would do it on Utilize,

1. Expand the configuration of the input/logic that you want to change the visibility of.
2. Enable the "Visibility Logic" toggle.
3. Select the property and the condition based on which you'd like to show the component.

{% hint style="info" %}
On the Details (*View One Item)*/Form (*Update One Item)* screens, you can also show/hide logic based on the current item's data.
{% endhint %}

### User input vs Current row based visibility

An "Form (Update One Item)" screen can both show the current row's data and update it. This means you can configure the *component visibility* based on either data already present in the row or what the user inputs. 

<figure><img src="/files/2jM9o3RTuduaS1piaOAu" alt=""><figcaption><p>Same property shown in two different components</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.notionapps.com/customize-app/component-visibility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.