> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/content/virtual-platform/programme/live-stream-settings-vp/youtube-stream-vp.md).

# YouTube Content

Add a YouTube video or live stream to your session(s) or virtual event lobby.

Add a YouTube video or live stream to your session(s) or virtual event lobby.

### **Add YouTube Content to Your Virtual Event Lobby**

1. Go to Settings > Virtual Event Settings > General > Lobby content
2. Select YouTube as the Lobby Content type.
3. Enter the YouTube URL
4. Save changes

***

### **Add YouTube Content to a Session**

You can add YouTube content when creating a new session or by editing an existing session.

1. Open the session.
2. Select **YouTube** as the **Session type**.
3. Enter the YouTube URL.
4. Click **Save Changes**.

#### Import via Excel

You can also add YouTube content using the session import file.

* Set the **Session Medium** column to `Youtube`.
* Enter the YouTube URL in the **Link to External Session Medium** column.

When imported, the YouTube content will be linked to the session automatically.


---

# 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://knowledge-base.letsgetdigital.com/the-admin-panel/content/virtual-platform/programme/live-stream-settings-vp/youtube-stream-vp.md?ask=<question>&goal=<user_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.