> 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/mixer-scene-parameters/and-include.md).

# \&include

Adds stream IDs within the viewer's room scope

Viewer-Side Option! ([`&scene`](/advanced-settings/mixer-scene-parameters/scene.md), [`&room`](/advanced-settings/setup-parameters/room.md))

## Options

Example: `&include=StreamID`

| Value       | Description                                                                  |
| ----------- | ---------------------------------------------------------------------------- |
| (stream ID) | Publisher stream ID within the viewer's room scope, with a matching password |

## Details

`&include` adds stream IDs to the viewer's selection, including alongside [`&view`](/advanced-settings/mixer-scene-parameters/view.md). It does not override room isolation.

* In a room, requested stream IDs resolve only to publishers in that same room. `&include` does not import standalone publishers or publishers from another room.
* Outside a room, `&include` can select additional standalone publishers with a matching password.

Matching stream IDs or passwords do not merge these scopes. Room isolation is intentional: common IDs such as `GUEST` or `TEST` must not cause an unrelated publisher's video to appear in a room.

Do not use `&include` to distribute one standalone publisher to guests in multiple rooms. A connection that happens to work because it was established before joining a room is not a supported way to bypass this restriction.

## Related

{% content-ref url="/pages/-MZdw7J4MWj\_hoTqT9Kh" %}
[\&view](/advanced-settings/mixer-scene-parameters/view.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZdurquJMMb6hjL98\_D" %}
[\&exclude](/advanced-settings/mixer-scene-parameters/and-exclude.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/mixer-scene-parameters/and-include.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.