> 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/whats-new/private-forms-in-deals.md). # Private Forms in Deals ### **Admins Private Documents Management** Our latest update on the Admins' Deals page includes an option that lets Admins make confidential forms private in the listing Checklist. This feature offers Admins an efficient way to securely share sensitive information. For example, commission forms can be shared with the other admins in the accounting department without agents having access to them. As an Admin, you can find the new Manage Access option in the drop-down menu in front of each Checklist task to specify whether agents can have access to that document or not. Once you uncheck the Agents option in the Manage Access modal, the Private label appears on that form. Also, all activities involving Chatroom information and update notifications will be visible to Admins only. {% hint style="info" %} When sharing something with the agents on a given deal, it's shared with just the primary and Co-Agents (if any) that are added to the deal. {% endhint %} {% embed url="" %} --- # 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://help.rechat.com/whats-new/private-forms-in-deals.md?ask=&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.