If Read has not been joining your Google meetings, you are at the right place. This article explains common issues and what to check.
As a first step, check your Reports > Incomplete tab to see what the error message is for the report you are looking for. An explanation for each of the error messages is listed below:
| Incomplete > Details | Explanation |
| Read not admitted to the meeting within 10 minutes of scheduled start time. | Read was not admitted or approved by an authenticated user. |
|
Read could not join the meeting because an authenticated user is required. or There is no eligible consenter in the meeting. For consumer meetings the initiator should be present; for workspace meetings at least one member of the owning organization should be in the call. |
The authenticated user(s) who can approve Read was(were) not in the meeting within 10 minutes after scheduled start time. See this section for more details: Who can approve Read during the meeting? |
| The Google Meet Media API has been disabled by an administrator. | See: Host > Google Workspace > Meet safety settings |
| The Google Meet Media API has been disabled by the host. | |
| A meeting participant stopped Read's recording session | A meeting participant removed Read from the meeting by clicking the "Stop sharing" button. |
Read could not join the meeting due to incompatible device requirements. |
Conference room devices often are not compatible due to the lack of ability to display the consent to record. |
Read left after no participants joined the meeting within 10 minutes of scheduled start time. |
No one was in the meeting within 10 minutes from the scheduled start time to approve recording. (For example, meeting rescheduled very close to the original start time, or the meeting started late.) |
| One or more devices in the conference are not compatible with Google Meet Media API (for example, an account may be under age). Read cannot join this meeting. |
Consent pop-up cannot be accepted on any conference room devices without a screen. If a meeting participant is underage, Read cannot record. Refer to Age restrictions (by Google). |
| When watermarking is enabled, Google Meet Media API cannot join this meeting. | Read AI also cannot record Meet calls that use a watermark. |
Details not listed or is empty?
Please reach out to us with the following meeting details so we can investigate:
- Meeting title, join link, meeting date/time and time zone
Who can approve Read during the meeting?
If you have invited Read to a meeting, and your Google account is not in a Google Workspace, you will need to be present in the meeting to give consent. (You are the 'initiator' in the screenshot from Google below.)

|
If the meeting host is on a personal @gmail.com account or does not belong to a Google workspace, they are the only one who will see the consent pop-up to allow Read to record. Make sure this host is logged in to their Gmail account when joining the meeting and not be late to the meeting. If the host did not join, Read would not be able to record even if you manually add Read using the meeting link. If the meeting host is a Google workspace account, this consent pop-up would be shown to only participants from the same domain. So if sam@read.ai is the host, only participants from @read.ai will see the consent and to be able to approve it. If the host the meeting using an incompatible device, for example, a conference room device, it is not able to consent Read to record. |
Host > Meeting invitation > settings
As the meeting host - Make sure to "Allow third-party apps to collect audio and video" under meeting activities
If you belong to a Google workspace, the Host controls > meeting activities > "Allow third party apps to collect audio and video" might be hidden from you if the admin disabled it in your Google workspace. Please reach out to the admin.
Host controls during the meeting
During the meeting, make sure the meeting host has this setting enabled in their "host controls":
Meet safety settings
The host's Google Workspace admin must confirm and adjust these settings to allow Read to join and record:
- In the admin portal, navigate to Apps > Google Workspace > Settings for Google Meet > Meet safety settings
-
Scroll to the bottom to locate the Media API settings. Make sure the affected user is under the organizational unit that this setting is applied to, for example, in the screenshot, on the left, the unit is called "read.ai", you might name your organization group something different, as long this user is under that unit, you are at the right place. Make sure this is turned ON.
-
Ensure that "Let third-party apps that join a Meet call use the audio and video of the call through Meet Media API" is checked.
- You can select either consent option below the checkbox. We recommend allowing "Everyone from the host's org can give consent". But if you choose "Only the host or co-host can give consent", they are the only ones who will see the permission dialog to allow Read to capture the meeting.
- Save changes
Other reasons why Read could not provide a report for a meeting
Note that calls that use Google's encryption feature cannot be recorded by Read AI
External links
Who can control Media API access in Google Meet?
If you get stuck on any issue, please contact the Read AI support team for help.