> 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/question-configuration/configure-option-questions.md).

# Configure Radio Button, Dropdown, or Check Box Questions

Insert a new question with desired type.

Insert a new question with desired type.

**Radio Button List** questions restrict respondents to a single answer.

**Dropdown List** questions restrict respondents to a single answer, but use less physical space on the page.

**Check Box List** questions allow respondents to select multiple answers.

Under the Question panel, insert question text and decide on options.

* The questions number by default, but you can override that by using the Question Code box.
* The colour picker allows you to specify the colour you want the question numbers appear on the survey.

Under Options panel, define your answer fields.

Set up more complex surveys by enabling Branches. Once Branches are enabled, configure the skip pattern by clicking the double arrow icon on the main question page.


---

# 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/question-configuration/configure-option-questions.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.