> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/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/engage/host-controls/restricting-a-session-to-group-members.md).
# Restricting a Session to group members
If you have host permissions in a Session that is owned by an Enterprise group, you can restrict access so that only members of that group can join. A Session is owned by an Enterprise group if a member of an Enterprise group created it, or if it's a persistent Session.
{% hint style="warning" %}
When this setting is turned on, any users who are in the Session but not a member of the group that owns the Session will be returned to the menu screen. This may include you.
{% endhint %}
{% hint style="info" %}
For more information about how to create and configure a persistent Session, see [Persistent and commercial Sessions](/engage/sessions/persistent-sessions.md). For information about how to create a standard Session that's owned by an Enterprise group, see [Creating a Session](/engage/sessions/creating-a-session.md).
{% endhint %}
To restrict access, complete the following steps:
1. In the Session, open the menu, and then select **Host Controls** 
.
2. On the **Host Controls** page, select **Session Settings**.
3. Scroll down to and turn on the **Restrict to group members only** toggle.
For persistent Sessions, this setting persists even after all users have left the Session.
---
# 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://docs.engagevr.io/engage/host-controls/restricting-a-session-to-group-members.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.