> 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-noclaim.md).

# \&noclaim

Join director mode without trying to claim the room as the main director.

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

## Aliases

* `&noautoclaim`
* `&nonclaiming`
* `&claim=0`

## Details

`&noclaim` lets a director-mode URL join without attempting to claim the room as the main director.

This applies to any director-mode link, including a co-director link:

```
https://vdo.ninja/?dir=MyRoom&codirector=DirectorPassword&noclaim
```

The co-director can still request co-director access from the current main director using the normal `&codirector` validation flow. The URL just skips the server-side room claim attempt.

## When to use it

Use `&noclaim` for co-director invite links when you want the current main director to remain the only room-claiming director.

This helps avoid a co-director becoming the main claimed director during reconnect or startup timing.

## Notes

* `&noclaim` does not grant co-director permissions by itself. Use [`&codirector`](/advanced-settings/director-parameters/codirector.md) for that.
* If a URL does not claim the room, claim-time settings such as [`&requireapproval`](/advanced-settings/director-parameters/and-requireapproval.md), [`&roomcap`](/advanced-settings/director-parameters/and-roomcap.md), and [`&roomkey`](/advanced-settings/director-parameters/and-roomkey.md) are not applied from that URL.
* The director room UI can generate a non-claiming co-director link from the co-director settings.

## Related

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

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