> 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/director-parameters/and-slotmode.md).

# \&slotmode

Gives you the possibility to assign slots to the connected guests

Director Option! ([`&director`](/advanced-settings/director-parameters/director.md))

## Details

Adding `&slotmode` to a director's URL gives you the possibility to assign slots to the connected guests. While the layout switching options of the [Video Mixer](/steves-helper-apps/mixer-app.md) will be missing when doing this as a normal director, you can still specify [`&layout`](/advanced-settings/mixer-scene-parameters/and-layout.md) via the URL for multiple scenes that will obey the slot assignments (might interest advanced users or inspire user suggestions).

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2FsCBLCoEVBC1PDvzOWE2b%2Fimage.png?alt=media&amp;token=9f90c9a1-4177-4f2f-80d4-9dddfb7f791a" alt=""><figcaption></figcaption></figure>

### Director Slot Behavior

By default, the director does **not** consume a slot when using `&slotmode`. This means:

* Guests are assigned slots starting from slot 1
* The director remains hidden from slot-based scene links (`&viewslot`)

If you want the director to appear in scenes and consume a slot, add [`&showdirector`](/advanced-settings/director-parameters/and-showdirector.md) to the director's URL:

```
&director=roomname&slotmode&showdirector
```

This is useful when the director is also a performer who should appear in slot-based layouts.

### Excluding Guests from Slots

Guests can use [`&slot=0`](/advanced-settings/settings-parameters/and-slot.md) to join the room without consuming a slot. This is useful for instructors, musicians, or control room operators who should not appear in slot-based scenes.

## Related

{% content-ref url="/pages/IZuV0MOnsFAJ1m68I30S" %}
[Mixer App](/steves-helper-apps/mixer-app.md)
{% endcontent-ref %}

{% content-ref url="/pages/BYPvlE2VwmCDC2WSudsu" %}
[\&slot](/advanced-settings/settings-parameters/and-slot.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/-MZdueo324IDjC0YD\_es" %}
[\&director](/advanced-settings/director-parameters/director.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/director-parameters/and-slotmode.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.