> For the complete documentation index, see [llms.txt](https://help.getcustomeriq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getcustomeriq.com/product-guides/meeting-recording/zoom-oauth-integration.md).

# Zoom OAuth Integration

## Recording Behavior

Zoom has formal requirements that bots must comply with in order to record meetings. In order to be compliant with Zoom, your meeting assistant can get recording consent one of two ways:

1. (Default) **Explicit consent**
2. OAuth permission

### Explicit consent

*By default*, in order for a bot to record Zoom calls:

* The host must be present in the meeting
* The host must explicitly grant permission to record by accepting the consent dialog

Because these requirements can introduce user friction and unexpected recording errors, we recommend using the provided OAuth permissions to grant recording permissions.

<figure><img src="/files/p111EQWfDfESxrDRbY8B" alt=""><figcaption><p>Use the Zoom OAuth feature in your Meeting Assistant configuration to avoid granting permission every meeting</p></figcaption></figure>

### OAuth permission

As an alternative to manually accepting a consent dialog each meeting, you can grant CustomerIQ OAuth permissions to allow bots to record **automatically**.

This means that not only will you not have to manually grant permission each meeting, but this also enables the assistant to record meetings regardless of if you are present for your meeting.

Because of this, we **highly recommend** using this mode of consent to make this process easier to implement into your workspace.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.getcustomeriq.com/product-guides/meeting-recording/zoom-oauth-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.