> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/surveys/configure-survey-details/conditions-tab.md).
# Conditions Tab
Add conditional logic to your survey.
Add conditional logic to your survey. This function hides a question on a subsequent page based on the answers of an earlier page (in case the condition is met or not met).
If Conditions have been enabled, you will see this icon :code-branch:beside the survey questions.
How to add an condition:
* Under the **Conditions tab**, click on the **Add Conditions** button.
* Select the question for which you want to define conditional logic so that another question on the survey is suppressed, depending upon the respondent's answer to it.
* Select the answer field value that will cause one or more subsequent questions to be suppressed. You can suppress only questions that appear on subsequent pages. You cannot suppress questions on the same page.
* Select the question that should be suppressed when a respondent selects the above answer field value.
* Click **Add Condition** button.
You must remove all responses before you can edit skip patterns, conditions, or branches. Remove responses under the Edit Survey/Details tab.
---
# 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.shiftiq.com/help/surveys/configure-survey-details/conditions-tab.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.