> 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/screenshare.md).

# Screenshare (Virtual event)

## The menu section

![](https://772941315-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M5LNCGpK5lyymcFZU4V%2F-Mbv0VqetqNjbE6a-y6o%2F-Mbv728pgwAl_PC5kCgR%2Fimage.png?alt=media\&token=75c5e3a6-2bfe-4c66-96df-5b326d4093e4)

By selecting the 'Screen Share' button the speaker is able to share the content visible on their screen. The options for screen sharing are sharing the entire screen, sharing an application window or sharing a tab of the browser. 

When speakers want to show a PowerPoint presentation in a Samba session via screen share, they must first set the Powerpoint to slide show on their computer/laptop before selecting the 'Screen Share' button. Otherwise, the presentation will not show in full screen.

{% hint style="danger" %}
**Be aware:**

* Screen sharing may interrupt the recording of the session. When you share your screen the audio from videos is not audible.
* Using the screen share function of Samba often causes the quality of the presentation to be affected due to the large quantity of bandwidth required by the attendees attending your presentation.
* Macbook users may experience issues sharing their screens. Hence, please make sure to test the function prior to the event.
  {% endhint %}


---

# 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/screenshare.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.