> For the complete documentation index, see [llms.txt](https://handbook.proanimal.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.proanimal.org/other/archived-pages/archive-social-and-community-events-guide/archive-event-role-checklists/archive-zoom-coordinator.md).

# \[ARCHIVE] Zoom Coordinator

As the Zoom Coordinator, you are responsible for managing a device that is connected to Zoom if the social is a hybrid event. Your role is to ensure a good experience for any online participants.

## Zoom Coordinator Checklist

Here are some suggestions to ensure things run smoothly:

* [ ] **Coordinate getting “host” access to the Zoom account** before the event. You can ask the organizer to assist with this
* [ ] **Bring a laptop** to use as the Zoom connection
* [ ] **Ensure you have wifi access** at the venue, coordinate with the host to make sure you can get online
* [ ] **Join the Zoom room 5 minutes before the announced start time** of the online portion of the event in order to avoid any last-minute technical issues
* [ ] **Troubleshoot any technical difficulties** (e.g. audio issues/echoing)
* [ ] **Hold the computer close to the presenter** during any announcements and programming in order to ensure the speaker is audible
* [ ] (Optional) **Facilitate breakout rooms in Zoom** for any trainings or programming that requires small group work
  * [ ] Breakout Rooms > Enter # of rooms & how to assign them > Create (more detailed instructions can be found [here](https://support.zoom.us/hc/en-us/articles/206476313-Managing-meeting-breakout-rooms))


---

# 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://handbook.proanimal.org/other/archived-pages/archive-social-and-community-events-guide/archive-event-role-checklists/archive-zoom-coordinator.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.