# \&codirector

Director Option! ([`&director`](https://docs.vdo.ninja/advanced-settings/director-parameters/director))

## Aliases

* `&directorpassword`
* `&dirpass`
* `&dp`

## Options

Example: `&codirector=DirectorPassword`

| Value                 | Description                                 |
| --------------------- | ------------------------------------------- |
| (no value given)      | Prompt for the co-director password on load |
| (alpha numeric value) | Shared co-director password                 |

## Details

Adding `&codirector` to the director URL enables trusted assistant-director access.

Example:

```
https://vdo.ninja/?director=MYROOMNAME&codirector=DirectorPWD123
```

Any other director using the same room name and matching co-director password can join as a co-director.

The first valid director in the room remains the main director. Co-directors inherit most director tools, but the main director remains authoritative and cannot be removed or controlled in the same way as other guests.

## Current behavior

* Co-directors can share most director controls
* The main director remains the authority
* Some controls remain restricted to avoid conflicts with the main director
* Queue and held-guest state is synced from the main director over the normal shared-state path

That last point matters for `&queue`: late-joining co-directors should still see the current "Activate Guest" controls for held guests, and activating a guest from a co-director routes through the normal director activation flow.

## Optional room-settings workflow

You can also enable co-directors from the room settings panel, which generates a co-director invite link for you.

## Warnings

* Do not reuse the room password as the co-director password.
* Co-directors can only join if the main director has enabled co-director mode with a matching password or room setting.
* If the main director leaves and rejoins, co-directors may need to reconnect and revalidate.
* If duplicating a director URL into another tab, remove any existing [`&push=STREAMID`](https://docs.vdo.ninja/advanced-settings/setup-parameters/push) value first, since each participant needs a unique stream ID.
* [`&view`](https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/view) can still be used to intentionally exempt specific stream IDs from queue behavior, but it is no longer the recommended workaround just to let co-directors see queued guests.

## Related

{% content-ref url="director" %}
[director](https://docs.vdo.ninja/advanced-settings/director-parameters/director)
{% endcontent-ref %}

{% content-ref url="and-hidecodirectors" %}
[and-hidecodirectors](https://docs.vdo.ninja/advanced-settings/director-parameters/and-hidecodirectors)
{% endcontent-ref %}

{% content-ref url="and-maindirectorpassword" %}
[and-maindirectorpassword](https://docs.vdo.ninja/advanced-settings/director-parameters/and-maindirectorpassword)
{% endcontent-ref %}