> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/types-of-custom-field/checkbox-list.md).

# Checkbox List

<figure><img src="/files/K88C1H5snmbYyfT0xwHI" alt=""><figcaption></figcaption></figure>

The checkbox list option works exactly like the checkbox field but allows you to create multiple checkboxes at the same time which, unlike a radio list, can be checked simultaneously.

The value field sets the value that the system will recognize, whilst the text field essentially functions as a title for the benefit of users. This means that the value field is mandatory and, if it is not populated, the system will recognize the item as being blank.

It is possible to set the value as different from the text, which lets you set a substantive value for the system with a shorter, simpler term for ease of use.

{% hint style="warning" %}
Do not duplicate any value fields, as this will not allow the system to function properly.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agilecase.com/administrator-documentation/types-of-custom-field/checkbox-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
