> For the complete documentation index, see [llms.txt](https://docs.milientsoftware.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.milientsoftware.com/help/quality-system/checklists/activating-control-column-in-a-checklist.md).
# Control column
When you create a new checklist, you can tick the checkbox "Control". This will decide if the control column should appear or not. This can also be changed after the creation.
The control column is meant to be used in checklists where you have identified requirements (often legal requirement), and your company is obliged to perform an internal secondary control of each checkpoint.
In the upper right corner of the checklist, you can define what person is in charge for doing the control. The selected person will receive an email notification when assigned. However, other users can also tick the checkboxes. Due to traceability in the quality system, the logged-in user's name (and date) will be logged when doing this action, even if you have set an overall person as responsible.
---
# 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.milientsoftware.com/help/quality-system/checklists/activating-control-column-in-a-checklist.md?ask=&goal=
```
`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.