> 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/speakers/recording.md).
# Recording (Virtual event)
## The menu section
Record a webinar by clicking the record button at the bottom left-side toolbar. Only the main interface will be recorded; menu items (like the chat) will not be recorded. Press the button again to stop recording. The button will flash yellow when the recording is starting. When you are recording the button will be red.
- Recording icon: When recording in the top-left corner of the menu this button will show.
{% hint style="info" %}
The recording is basically a screen recording of the person who activated the recording button. Hence, the person who activated the recording should not leave the session while recording.
**Please note:** a single video recording has a max time limit of 4 hours.
{% endhint %}
The recording of a session will be saved to share with attendees after the event. The recordings will be posted in the admin panel under 'Recordings'.
---
# 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/speakers/recording.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.
