> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/tour/access-control/groups.md).

# Groups

Where roles control the types of data a user can se, groups control which data records a particular user has access to. This is less important in a small company, but as your organization grows there are several reasons to protect data.

* Sensitive data may require special security clearance
* Prevent employees or contractors from stealing data
* Time-sensitive data may need to be kept under wraps for a period of time

Bunny's uses a group hierarchy to protect data. Users can see anything that's attached to the nodes below them, but they can't see up. Consider the following example:

        Global Sales\
&#x20;               North American Sales                <-- Bob sits here\
&#x20;                       East Coast\
&#x20;                       Mid West\
&#x20;                       West Coast\
&#x20;               Government Sales\
&#x20;               European Sales\
&#x20;               APAC Sales

If Bob belongs to the North American Sales group he can see all data that belongs to that group or the three regions below it, but he can't see Global Sales, Government Sales, European Sales or APAC Sales.&#x20;

The objects in Bunny that can be controlled by groups are:

* Leads
* Accounts

When a user creates any of those objects, their default group membership will be the group the user belongs to.


---

# 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.bunny.com/guide/tour/access-control/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.