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

# Conditions

{% hint style="warning" %}
You'll find all conditions-related settings in the "Options" card "Show/hide" tab.
{% endhint %}

## Where they can be placed

* Conditions on buttons
* Conditions on components
* Conditions on pages

## Types of conditions

* Is / Includes: It means the component will be displayed if another component is or includes any of the selected value/s.
* Is Not / Does Not Include: It means the component will be displayed if another component isn't or doesn't include any of the selected value/s.
* Exists: It means the component will be displayed if another component exists or has a value.
* Does Not Exist: It means the component will be displayed if another component doesn't exist or doesn't have a value.

## Example use-cases

* Showing a "We don't work in your area" or "You must be older than 18" page if the user's input doesn't match your requirements, hide it if it does. 
* Create a couple of groups of bullet points describing the different service plans you're offering. Show one or the other depending on the plan you recommend for the user.
* You can have a Stripe component for subscriptions, another for one-time payments, and another one for collecting card details. You can hide the ones you don't need for a particular customer.

{% hint style="warning" %}
If more than one condition is added to a page, component, or button, both conditions need to be true for the component to be displayed.
{% endhint %}

{% hint style="info" %}
Tip: An alternative way to Hide components, pages or buttons is toggling on "Hide Page"/"Hide Component"/"Hide Button".
{% endhint %}

## Related Docs:

<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><mark style="color:blue;"><strong>How to set show/hide conditions</strong></mark></td><td><a href="/files/6xbUJ0PWSpYEYORNgkI0">/files/6xbUJ0PWSpYEYORNgkI0</a></td><td><a href="/pages/JZtFiBSRdOwWfWIMo29H">/pages/JZtFiBSRdOwWfWIMo29H</a></td></tr><tr><td align="center"><mark style="color:blue;"><strong>How to hide a global component on a specific page</strong></mark></td><td><a href="/files/6gD79yoB42n1Cj2nMCWs">/files/6gD79yoB42n1Cj2nMCWs</a></td><td><a href="/pages/5Tg5HCf696Ggsv2zmtji">/pages/5Tg5HCf696Ggsv2zmtji</a></td></tr><tr><td align="center"><mark style="color:blue;"><strong>How to display a value previously entered by the user</strong></mark></td><td><a href="/files/ICS5CMWRSXS5pDqEWHKo">/files/ICS5CMWRSXS5pDqEWHKo</a></td><td><a href="/pages/fj0Fl4ROfovHqNGyaBdC">/pages/fj0Fl4ROfovHqNGyaBdC</a></td></tr></tbody></table>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.trysavvy.com/other-useful-docs/useful-docs/conditions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.