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

# \&approvepopup

Show a director confirmation popup when a guest is waiting for approval.

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

## Aliases

* `&approvalpopup`

## Details

`&approvepopup` shows an opt-in confirmation popup when a guest or scene request is waiting for server-side room approval.

It is intended to be used with [`&requireapproval`](/advanced-settings/director-parameters/and-requireapproval.md):

```
https://vdo.ninja/?director=MyRoom&requireapproval&approvepopup
```

Without `&approvepopup`, pending join requests are still shown in the director controls, but the director is not interrupted by a modal confirmation prompt.

## What the popup does

When a pending join request arrives, the director sees a confirmation dialog. Approving admits the guest. Denying rejects the pending join request.

If the request is for a scene/view role rather than a guest, the popup labels it as a scene request.

## What it does not do

`&approvepopup` does not create the approval queue by itself. Use [`&requireapproval`](/advanced-settings/director-parameters/and-requireapproval.md) for that.

`&approvepopup` does not enable audio alerts, notification sounds, or system toasts. Add [`&notify`](/advanced-settings/settings-parameters/and-notify.md) or `&beep` for sound.

## Related

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

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