> For the complete documentation index, see [llms.txt](https://yudu-sentinel.gitbook.io/sentinel-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yudu-sentinel.gitbook.io/sentinel-documentation/spaces/video-conference.md).

# Video Conference

Navigate to  Video Conference management at **/spaces/conferences**

From here you can view all current and previous Video Conferences.

<div data-with-frame="true"><figure><img src="/files/SlIUtVS0NyDMAv8HWjGQ" alt=""><figcaption></figcaption></figure></div>

There are 2 types of Video Conference: Ad-Hoc and Scheduled.

### Ad-Hoc Conferences

Ad-Hoc Conferences are for spur of the moment meetings.

If you need to quickly get people on a call - create an Ad-Hoc Conference, share the conference link and all participants can be on the call within in minutes.

### Scheduled Conferences

Scheduled Conferences are exactly the same as Ad-Hoc however they take place within specified start and end times. Use scheduled conferences to plan for future meetings and send out conferences link well ahead of time. The meeting's calendar links can be download and share with meeting participants.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://yudu-sentinel.gitbook.io/sentinel-documentation/spaces/video-conference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.