> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/single-choice-choice.md).

# Single-choice (Choice)

Let users select one value from a fixed list.

Use a **Single-choice** field when users should pick one value from a fixed list, such as a status, category, or stage.

For the general settings all data fields have in common, see [Shared field settings](/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/shared-field-settings.md).

Field-specific settings for **Single-choice** are:

#### Everywhere

* **Default value**: preselects one option in new records

**Display**

* **Choices**: defines the available choices
  * **Name**: the text value or description of the choice 
  * **ID**: the internal ID, change it carefully when you run logic ferring to it
  * **Color**: assigns a color to each choice
  * **Icon**: assigns an icon to each choice
* Use the **`⋮⋮`** handle on the left of each choice to change the order
* **+ Add option**: creates more options

#### On the form

* **Display as**: shows the choices as a **Combobox**, **Radio button**, or **Tabs**

{% hint style="info" %}
Use **Single-choice** when users should select exactly one value. If users should be able to select several values, use **Multi-choice** instead.
{% endhint %}


---

# 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.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/single-choice-choice.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.