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

# \&codirector

Allows assistant directors to join the director room with a shared co-director password and a subset of protected controls.

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

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

The room settings panel can also generate a non-claiming co-director link. This adds [`&noclaim`](/advanced-settings/director-parameters/and-noclaim.md), so the co-director joins director mode without trying to claim the room as the main director.

## 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`](/advanced-settings/setup-parameters/push.md) value first, since each participant needs a unique stream ID.
* [`&view`](/advanced-settings/mixer-scene-parameters/view.md) 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="/pages/-MZdueo324IDjC0YD\_es" %}
[\&director](/advanced-settings/director-parameters/director.md)
{% endcontent-ref %}

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

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

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