> 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-screen-alpha.md).

# \&screen

The guest can see and hear the director before being activated into the room.

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

## Aliases

* `&queue2`

## Details

`&screen` restores the older guest-approval behavior that base [`&queue`](/advanced-settings/guest-queuing-parameters/queue.md) used to provide.

With `&screen`, the guest can see and hear the director before activation, but they are still not admitted into the room with the other guests until the director activates or transfers them.

Use this when you want a quick pre-show screening conversation without running the full room in screening-room mode.

This mode applies to guest invite links, not to the director link running the room in `&queue` mode.

Transferring the guest to another room also counts as activation.

## Related

{% content-ref url="/pages/-MZX-3ygkLfjNFzYFAbU" %}
[\&queue](/advanced-settings/guest-queuing-parameters/queue.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-screen-alpha.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.