> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/design-and-structure/components-visibility/conditional-visibility/examples/hiding-a-component-using-multiple-conditions.md).

# Hiding a component using multiple conditions

Sometimes you may want to use multiple conditions when setting conditional visibility for a component. An easy way to do this is to use logical operator formulas like `AND()`, `OR()`, and `NOT()`.

In this example, I will use `AND()` to make my purchases table visible *only* when the selected customer has a status of *Active* and true for *Is Approved.* If either of these conditions is not met, the purchases table will not be visible.

1. To set up conditional visibility using multiple conditions, start the same way as in other examples – click on the component you wish to make conditionally visible, then go to the *Display* section in the component menu.&#x20;
2. In the *Conditional Visibility* field, first choose the logical operator formula that you want to use. In this example, that will be `AND()`.
3. Next, enter the conditions that you want to use with the logical operator.\
   \
   In this example, *Is Approved* is a checkbox – so it will already return *True* or *False* – but *Status* is a text field, so I will need to use the `EQ()` formula to return *True* or *False.*&#x63;hoose the user property that you want to use. Because my property type is a checkbox, it already returns `True` or `False` based on its value.&#x20;

When I have set this up correctly, the value in the *Conditional Visibility* field will be:\
\
`=AND(elements.Customers["0"].selected_item["Is Approved"], EQ(elements.Customers["0"].selected_item.status, "Active"))`

{% hint style="info" %}
Now the purchases table will only appear when a user is selected  who is approved and also *Active.*
{% endhint %}

App builder view:

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FB0dWkohu8dPQQv5YOkrl%2FUntitled14.gif?alt=media&amp;token=ffc98034-4274-4905-b831-99d0ca14c47f" alt=""><figcaption></figcaption></figure>

App view:

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FomGoIEZxKoyoHwHEDJyd%2FUntitled15.gif?alt=media&amp;token=1cedfca5-573d-4faa-bd14-c23b765fa413" alt=""><figcaption></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/classic-app-builder/design-and-structure/components-visibility/conditional-visibility/examples/hiding-a-component-using-multiple-conditions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
