> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/appendix/brokerage-set-up/transaction-management-deals/setting-up-deals/creating-checklists/controlling-visibility.md).
# Controlling Visibility
In every checklist, not all items need to be visible to agents. Some forms, tasks, or notes are internal to the brokerage, designed for compliance, accounting, or management review.
With **visibility controls**, Admins can decide whether an item is seen by **Agents**, **Back Office/Admins only**, or **both**. This ensures the right people see the right information at the right time.
**Step 1:** Navigate to Checklists\
Go to **Deals Settings** → **Checklists** and open the checklist you want to configure.
**Step 2:** Locate the Item\
Scroll to the **Forms** or **Tasks** section of your checklist.
**Step 3:** Open Access Controls\
Find the **Access** column. Click the dropdown menu beside the checklist item.
**Select Access Level**
* **Agents** → The item will be visible to agents in their Deals.
* **Back Office** → Only brokerage admins and management can view/complete the item.
* **Agents & Back Office** → Both agents and admins can see and work on the item.
---
# 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://help.rechat.com/appendix/brokerage-set-up/transaction-management-deals/setting-up-deals/creating-checklists/controlling-visibility.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.
