> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/scheduling/meetings.md). # Find and manage meetings Open **Bookings** to find meetings across the workspace. Use the list for detailed filters and the calendar for the schedule by day, week or month. ## Find a meeting Search for the guest or meeting and filter by status, date, host, event, location or duration where shown. Use the coming-up options to focus on the next 24 hours or next 7, 14 or 30 days. Open the meeting to review its host, guests, local time, description and current status. Confirm the correct meeting before taking an action. ## Manage it * **Join** opens the conference link when one exists. * **Reschedule** moves the meeting through its supported reschedule flow. * **Hand off** changes the host through the reassignment flow. * **Cancel** updates the meeting and sends the configured cancellation notices. * **Mark no-show** records a missed meeting. Actions depend on your role, meeting ownership, state and source. See [Reschedule or hand off](/scheduling/manage-meetings.md). ## Act on several meetings Select eligible rows to show the bulk action bar. Review the selection before Mark no-show or Cancel meetings, and enter a cancellation reason if appropriate. The result can report changed and skipped meetings separately. Changing a meeting's status is separate from editing an event type. Event settings affect booking behavior; the meeting record describes what happened to that particular booking. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/scheduling/meetings.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 `build a script that syncs our docs to a CMS` 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.