> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/forms/form-elements/form-features-conditional-visibility.md).
# Form Features - Conditional Visibility
## Overview
{% hint style="info" %}
SharinPix Form Elements can be configured to be visible only when a particular condition is met. This configuration is available in the [SharinPix Form Builder](/forms/form-elements/sharinpix-form-template-editor.md).
This article covers the following:
* [How to configure a Visibility Condition](#configure-visibility-conditions)
* [Demo of the Conditional Visibility feature with an Air Conditioning Inspection Example](#demo-air-conditioning-inspection-example)
{% endhint %}
## Getting Started
### Configure Visibility Conditions
The visibility condition of a SharinPix Form Element can be configured using the "**visible when**" field in the SharinPix Form Builder.
This field can be found in the advanced tab for Question elements and takes as input an expression that evaluates to True or False (boolean).
{% hint style="success" %}
Tips:
For more information on the Functions and Expressions of the Visibility Feature, please follow the article below: [Form Formulas](/forms/form-elements/sharinpix-form-formula-functions-and-operators.md)
{% endhint %}
### Submit answer even when hidden
Use **Submit answer even when hidden** to submit one question's answer when it is hidden.
Questions can be hidden by a visibility condition. By default, answers to hidden questions are not included in a submitted response. They do not reach Salesforce.
The form-level **Include hidden fields in Response** setting controls this default. **Submit answer even when hidden** overrides it for one question. Other hidden questions keep the form's default behavior.
#### Turn on the option
1. Open the form template in the **Form Template Editor**.
2. Select the question you want to configure.
3. Open the question's **Advanced** tab.
4. Select **Submit answer even when hidden**.
*Screenshot: Submit answer even when hidden in the Advanced tab.*
5. Save and activate the new template version.
{% hint style="info" %}
**Good to know**
* If the question is inside a hidden section, enable the same option on the section. This keeps the answer in its response location.
{% endhint %}
### Demo: Air Conditioning Inspection Example
This example demonstrates the Conditional Visibility feature within an Air Conditioning Inspection example. If damage is detected, additional fields will be visible to provide more information on the damage.
The example below shows a *textarea* element - *'Describe the damage'* , configured with a visibility condition. This element will only be visible when the value of the previous question, *'Are there any signs of damage?'* , is equal to *'Yes'*.
The diagram below shows the form with the questions 'Is the unit operating properly?' and 'Are there any signs of damage?' only and the elements with conditional visibility not showing.
The diagram below shows the form with the two additional questions that became visible when the *'Is the unit operating properly?'* question was set to '*No*' and *'Are there any signs of damage?'* question was set to *'Yes'*.
---
# 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.sharinpix.com/forms/form-elements/form-features-conditional-visibility.md?ask=&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.
