> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/adding-videos-to-pages-admins.md).

# Adding Videos to Pages (Admins)

Brokerage Admins can now embed videos directly into Pages using the built-in editor. This makes it easier to share training videos, leadership messages, and policy explanations.

You can now add videos to Pages using a **video URL**, no uploading required.

**Supported video sources:**

* YouTube
* Vimeo
* Direct video files (MP4)

Videos are embedded directly into the page and playable inline for agents.

### How to Add a Video to a Page

1. Go to **Support → Pages**
2. Create a new page or edit an existing one
3. In the editor toolbar, select **Insert Video**
4. Paste the video URL (YouTube, Vimeo, or direct MP4)
5. Save your page

That’s it. The video automatically embeds and displays for agents.


---

# 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://help.rechat.com/whats-new/adding-videos-to-pages-admins.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.