> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/advanced-settings/screen-share-parameters/and-allowscreenmedia.md).

# \&allowscreenvideo / \&allowscreenaudio

Allow or block incoming screen-share video and audio on a viewer link

Viewer-Side Option! ([`&view`](https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/view.md), [`&scene`](https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/scene.md), [`&room`](https://docs.vdo.ninja/advanced-settings/setup-parameters/room.md))

These two parameters override whether this viewer accepts screen-share video or screen-share audio. Camera video and microphone audio are not affected.

## Options

| Parameter           | Value                              | Result                    |
| ------------------- | ---------------------------------- | ------------------------- |
| `&allowscreenvideo` | no value, `1`, `true`, `yes`, `on` | Accept screen-share video |
|                     | `0`, `false`, `no`, `off`, `none`  | Block screen-share video  |
| `&allowscreenaudio` | no value, `1`, `true`, `yes`, `on` | Accept screen-share audio |
|                     | `0`, `false`, `no`, `off`, `none`  | Block screen-share audio  |

Unrecognized values count as "accept". Without these parameters, the normal rules apply.

## Details

* A `&view` link only loads a publisher's screen share when its stream ID ends in `:s`, such as `&view=STREAMID:s` (see [`&screensharetype`](https://docs.vdo.ninja/advanced-settings/screen-share-parameters/and-screensharetype.md)). `&allowscreenvideo` and `&allowscreenaudio` override that rule in either direction.
* [`&noscreenshare`](https://docs.vdo.ninja/advanced-settings/screen-share-parameters/and-noscreenshare.md) takes priority. When it is present, screen shares stay blocked.
* [`&novideo`](https://docs.vdo.ninja/advanced-settings/video-parameters/and-novideo.md), [`&noaudio`](https://docs.vdo.ninja/advanced-settings/audio-parameters/noaudio.md) and `&broadcast` can still block a track that these parameters accept.

## Examples

Load a guest's screen share without its audio:

`https://vdo.ninja/?view=STREAMID:s&allowscreenaudio=0`

Show screen shares in a group scene, but mute their audio:

`https://vdo.ninja/?scene=0&room=ROOMNAME&allowscreenaudio=0`

## Related

{% content-ref url="/pages/Pu9zYqvWHZ1WXWEOxi37" %}
[\&noscreenshare](https://docs.vdo.ninja/advanced-settings/screen-share-parameters/and-noscreenshare.md)
{% endcontent-ref %}

{% content-ref url="/pages/CGcri2JHEp7BuaSi6gXN" %}
[\&screensharetype](https://docs.vdo.ninja/advanced-settings/screen-share-parameters/and-screensharetype.md)
{% endcontent-ref %}


---

# 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://docs.vdo.ninja/advanced-settings/screen-share-parameters/and-allowscreenmedia.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.
