> 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-muteall.md). # \&muteall Adds a director-only button for muting or unmuting all current guests. Director Option! ([`&director`](/advanced-settings/director-parameters/director.md)) ## Aliases * `&muteallguests` * `&muteguests` ## Details `&muteall` adds a top-bar button in the director control room for muting or unmuting all connected guests at once. ``` https://vdo.ninja/?director=MyRoom&muteall ``` The button uses the same remote guest mute path as each guest's individual **Mute** button in the director UI. When active, newly joining guests are also muted once their director control box is created. ## Limitations This option is URL gated. If `&muteall`, `&muteallguests`, or `&muteguests` is not added to the director URL, the button stays hidden and the app behaves as it normally does. The global mute state is live browser state. It is not a room-level saved setting, and it starts inactive again if the director page is refreshed. Manual per-guest changes are still allowed. If a director manually unmutes one guest while the global mute-all button remains active, that guest stays unmuted until another global mute-all action or another audio-follow action changes them. New guests will still be muted while the global mute-all state is active. If [`&highlightmute`](/advanced-settings/director-parameters/and-highlightmute.md) / **Mute follows Highlight** is also active, Highlight can still unmute the highlighted guest. In that combination, `&muteall` is not an absolute lockout. The button targets normal guest audio controls only. It skips directors, screen-share entries, pseudo-guests, and guests that do not yet have a director mute control available. ## Related {% content-ref url="/pages/OwSBdNM1Zpv6fRu9OHug" %} [\&blindall](/advanced-settings/director-parameters/and-blindall.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-muteall.md?ask=&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.