> 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/guest-queuing-parameters/and-queuetransfer.md).

# \&queuetransfer

Keep a transferred guest queued in the destination room until activated.

Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md), [`&room`](/advanced-settings/setup-parameters/room.md))

## Aliases

* `&qt`

## Details

`&queuetransfer` changes what happens after a guest is transferred from one room to another.

Normally, a transferred guest is admitted into the destination room immediately if the destination room accepts the transfer. With `&queuetransfer` on the guest invite link, the guest lands in the destination room's queue flow instead, so the destination director can activate them when ready.

Guest invite link:

```
https://vdo.ninja/?room=LobbyRoom&queuetransfer
```

When the lobby director transfers this guest to another room, the guest arrives there in queue mode rather than going live immediately.

This is useful when a public lobby director is routing guests into production rooms, breakout rooms, or private green rooms, but the destination director still wants final control.

## Interaction with room admission approval

`&queuetransfer` is a queue workflow option.

If the destination room also uses [`&requireapproval`](/advanced-settings/director-parameters/and-requireapproval.md), the transferred guest remains pending until the destination director approves them.

If the destination room has [`&roomcap`](/advanced-settings/director-parameters/and-roomcap.md) and is full, the transfer is rejected.

## Related

{% content-ref url="/pages/-MZX-3ygkLfjNFzYFAbU" %}
[\&queue](/advanced-settings/guest-queuing-parameters/queue.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M\_GN9YKWH8VJmAwHOek" %}
[How to transfer guests to other rooms](/guides/transfer-rooms.md)
{% endcontent-ref %}

{% content-ref url="/pages/CdV7XfS7kF1iejAVFibl" %}
[\&requireapproval](/advanced-settings/director-parameters/and-requireapproval.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/guest-queuing-parameters/and-queuetransfer.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.