> 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/adding-a-co-host.md).
# Adding a co-host
When you start a Session, you are given the role of host. You can choose to give host permissions to any other person in the Session. However, because hosts have the highest possible permissions in a Session, we recommend that you give the permission only to people that you know and trust.
{% hint style="warning" %}
You can't make a LITE user a co-host.
{% endhint %}
{% hint style="warning" %}
If you're in a persistent Session and you give host permissions to a member of the Enterprise group that owns the persistent Session, that person remains a host the next time that they join the persistent Session.
{% endhint %}
You may want to assign another user as co-host to guard against unexpected technical issues. For example, if you are the only host in a standard Session, and you lose your network connection, everyone else in the Session is returned to the menu screen.
To add someone as a co-host, complete the following steps:
1\. Open the menu, select **Host Controls** , and then select the **Users** tab.
2\. Identify a user and select their **More** icon .
More icon for an individual user
3\. On the **Host Actions** page, select **Add Co-Host**.
Option to add a co-host
---
# 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/adding-a-co-host.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.
, and then select the **Users** tab.
2\. Identify a user and select their **More** icon 
.
