> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/spot-content/lives/start-a-live.md).

# Start a live

Quiet on set, It's rolling!

## Starting a live session 

To start a live session, go to the Live Room : 

* Click on `Enter the studio`. 
* Set your participation parameters (camera, microphone, etc.). 
* Click on `Participate`. 
* Click on `Start Live`. 
* If you choose to start your live show before the start date, you will need to tick the "I want to start my live show early" box. 
* Click on `Start live`. 

{% hint style="info" %}
Only live host speakers can start a live.
{% endhint %}

{% embed url="<https://vimeo.com/834389728/dff68839d2?share=copy>" %}

## Sharing your screen&#x20;

When you join the studio as a speaker or workshop participant, you can share your screen by clicking on the `Share` icon.&#x20;

📢 If you are sharing a video with audio, make sure you share the system audio as well.

## Access the studio settings&#x20;

Go to settings ⚙ at the top left of the studio to:

* Change the background effect.&#x20;
* Change the audio and video source.

{% embed url="<https://vimeo.com/834396016/d7c7cf951f?share=copy>" %}


---

# 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.meltingspot.io/english/spot-content/lives/start-a-live.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.