> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/~/revisions/T8G3F1S1kUWJiGQZsj4F/wiki/infrastructure/zoom.md). # Video conferences ## Google Meet Through Google for Nonprofits, CorrelAid has access to premium Google Meet features. Those include up to 100 participants, breakout rooms, whiteboards, and many more. [See here](https://www.google.com/nonprofits/workspace/compare/) for an overview. If you need to record a meeting (e.g. a meetup), you need to use Zoom instead. If you have a [Google Workspace](/~/revisions/T8G3F1S1kUWJiGQZsj4F/wiki/infrastructure/google-workspace.md) account, you can create Meets by going to . Alternatively, you can directly add Google Meets to calendar events you create in your personal [CorrelAid calendar](/~/revisions/T8G3F1S1kUWJiGQZsj4F/wiki/infrastructure/google-workspace.md#personal-calendar). ## Zoom CorrelAid has two Zoom pro licenses. If you want to have a link for an event, please contact our [community manager](https://app.mural.co/t/correlaid3823/m/correlaid3823/1699870589469/4cf3017ee7f487ebbf5ba4efff6245a8d0ed4569?sender=u1b832a9670bb15a61a279564) on Slack. ### Recording a Zoom event Sometimes, you might want to record a Zoom event. Here are our recommendations to keep the identities of the participants out of the recording: * the speaker should share their screen * host: switch to speaker view (**not** gallery) * host: use the **spotlight** feature to spotlight the speaker and the moderator (typically the host functions as the moderator) * with this setup... * participants can ask questions without appearing in the recording * the host can have the chat open overlaying the zoom recording -> this is independent of the recording feature --- # 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.correlaid.org/~/revisions/T8G3F1S1kUWJiGQZsj4F/wiki/infrastructure/zoom.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.