> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/enterprise/enterprise-admin-portal/managing-subgroups.md).

# Subgroups

ENGAGE supports two levels of groups: top-level groups and subgroups. A top-level group can have subgroups. A subgroup can’t have any further subgroups.

You can use subgroups for separate cohorts of members. For example, you could create separate subgroups for different clients, departments in your organization, or permissions that you want to assign. Some example uses are as follows:

* Create Sessions or Events that only appear to a specific group of people. For example, so that humanities students see only humanities classes and social science students see only social science classes.
* Assign a custom name and branding to a subgroup. For example, a client’s company name and logo.
* Create an administrative subgroup. For example, with options enabled to create persistent Sessions and Events.
* Create a limited access subgroup. For example, to disable the options to see public content in the ENGAGE app.


---

# 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.engagevr.io/enterprise/enterprise-admin-portal/managing-subgroups.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.