> For the complete documentation index, see [llms.txt](https://docs.spreo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spreo.io/boards/design-and-meeting-mode.md).

# Meeting Mode

Start a meeting on a board to become the Host and unlock the facilitation tools.

Meeting Mode can be activated at any time on a board, by any licensed team member.

While you can collaborate on a board without activating Meeting Mode, it is specifically designed for collaborating with others. Meeting mode enables a unique set of meeting host / facilitation controls, and the left toolbar changes to focus collaboration tools.

Read our [Toolbar guide](/boards/the-tools.md) for full details of what each tool does.

<figure><img src="https://2875185778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwEhLPSRTDuhd61395hZu%2Fuploads%2F14PEEjuWxrauth2l6KbK%2Fswitch-to-meeting-mode.png?alt=media&amp;token=f5110632-75eb-4771-8b83-974a081049a5" alt=""><figcaption></figcaption></figure>

When you start Meeting Mode on a board, you become the Host and get access to [Host controls](/boards/host-controls.md) at the top of the board. Everyone else becomes a participant.

{% hint style="info" %}
As the Host you can edit Super Lock during Meeting Mode, and expand your toolbar to edit the board layout.
{% endhint %}


---

# 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.spreo.io/boards/design-and-meeting-mode.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.
