> 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/color.md).

# Color

Store a color value for views, charts, and visual display.

Use a **Color** field when the record should store a color value that you can reuse in views, charts, or dynamic choice fields.

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).

**Color** uses the shared settings only. It does not add extra field-specific options.

In the color picker, users can:

* choose a preset color
* use the color mixer by clicking the color preview next to the color value field
* enter a custom color as a hex value, such as `#ff0000`
* enter a custom color as an RGB value, such as `rgb(255, 0, 0)`
* enter a color name, such as `red`
* remove the current color

Click **Confirm** to apply the selected color.

Use a **Color** field when records should control how items appear in views such as **Calendar**, **Kanban**, **Gallery**, or **Maps**. See [Work with views](/builder-hub/visualize-and-organize-your-data/work-with-views.md).

{% hint style="info" %}
Use a **Color** field when the value should drive visual display in the app.

If users should choose from a fixed list of named options with assigned colors instead, use **Single-choice** or **Multi-choice**.
{% 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/color.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.