> 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/locking-a-session-or-event.md).
# Locking a Session or Event
As a host, you can lock a Session or Event so that no additional users can join. For example, to hold a private conversation with another user or to prepare an Event space without risk of interruption.
{% hint style="warning" %}
For standard Sessions and Events, the person that creates the Session or Event is the only person that can lock and unlock it. For persistent and scalable Sessions, any host can lock and unlock the Session.
{% endhint %}
To lock or unlock a Session or Event, complete the following steps:
1. In the Session or Event, open the menu, and then select **Host Controls** .
2. On the **Host Controls** page, select the **Host Actions** tab.
3. Turn the **Lock** toggle on to prevent users from joining or off to allow users to join.
Option to lock and unlock a Session
{% hint style="info" %}
Persistent and scalable Sessions unlock automatically after the last person leaves.
{% endhint %}
{% hint style="info" %}
If there are multiple hosts in a standard Session, and the person that created the Session locks it and then leaves, the Session will remain locked and nobody will be able to join. However, an exception is made for the person that created the Session, who is able to re-join the Session, and can then choose to unlock it.
{% endhint %}
---
# 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/locking-a-session-or-event.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.
.
2. On the **Host Controls** page, select the **Host Actions** tab.
3. Turn the **Lock** toggle on to prevent users from joining or off to allow users to join.