> For the complete documentation index, see [llms.txt](https://docs.compliancebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.compliancebot.io/settings/accessing-settings/document-groups.md).

# Document Groups

A <mark style="color:blue;">**Document Group**</mark> is a categorized collection of related documents that are grouped together based on their purpose, type, or usage within an organization. It helps in organizing, managing, and controlling access to documents for streamlined workflows and better compliance management.

Create Document Group-

<mark style="color:orange;">**Name:**</mark>\
The title or label for the document group (e.g., "Policy Documents", "Client Agreements", "Employee Records").

<mark style="color:orange;">**Description:**</mark>\
A detailed explanation of the purpose of the document group and the types of documents it includes (e.g., "Policy Documents: This group contains all company policies, including Code of Conduct, IT Security Policies, and Data Privacy Guidelines.").

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


---

# 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.compliancebot.io/settings/accessing-settings/document-groups.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.