- Connect separate Google, Outlook, and Zoom calendars
- Share calendars on the Google/Outlook side
- Logging in to Read from multiple SSO accounts
You may have multiple different email addresses and calendars with meetings that you want to be able to use Read with. Read does not allow users to connect an infinite number of different email/calendar accounts to a single Read account, however there are some options that may allow you to use your Read account across multiple calendars.
Connect separate Google, Outlook, and Zoom calendars
Read allows users to connect separate accounts for their Google, Microsoft Outlook, and Zoom calendars, by going to Account Settings > Calendar. You can connect one account for each of these integrations.
If you have any meetings that exist on more than one of these calendars (e.g. if you sync your Zoom calendar to your Google account), Read will show multiple instances on your Calendar page, however Read will recognize that these are the same meeting and only deploy one instance of the Assistant to the call when it occurs.
If you use Google or Microsoft icon for single sign-on, note that you can use a different account for your connected calendars if you want (the same is not true for Zoom). You cannot connect more than one Google, Microsoft, or Zoom account for your connected calendars, but you can always disconnect your current one and connect a new one under Account Settings > Calendar.
Share calendars on the Google/Outlook side
A single Google Calendar or Microsoft Outlook account can contain multiple different calendars within it. Read will try to pull in all calendars that are listed under the "My calendars" section in Google Calendar and Outlook.
You can see these calendars and turn them on or off individually for syncing with Read on your Apps & Integrations page:
If you have multiple different Google and/or Outlook accounts that you want to use with Read, you may be able to share your calendars with your main account (the one connected to Read) through Google or Outlook.
- This Google support article explains how to share your calendar from one account to another.
- Shared calendars will typically appear under "Other calendars" at first. You will need to get them under "My calendars" in order for Read to be able to sync with them. Google has an FAQ about this here.
- After sharing, you should see the calendars listed under Apps & Integrations > Google Calendar. Make sure to turn your new calendar(s) on for syncing.
- If you don't see the new calendars, we recommend disconnecting and reconnecting your calendar account to force a refresh.
Outlook
- This Microsoft support article explains how to share your calendar from one account to another. We recommend sharing with maximum permissions to help avoid issues.
- Like with Google, shared calendars must be listed under "My calendars" in Outlook in order for Read to be able to sync with them.
- This will also only work if the account that you have connected to Read is a paid (i.e. work/school) Outlook account.
- After sharing, you should see the calendars listed under Apps & Integrations > Microsoft Outlook. Make sure to turn your new calendar(s) on for syncing.
- If you don't see the new calendars, we recommend disconnecting and reconnecting your calendar account to force a refresh.
Logging in to Read from multiple SSO accounts
All Read accounts have a single "primary" email address, which is initially just the address that you used when creating the account. However you can add (and remove) additional login methods to your account via your Account Settings > Profile & Account. Just click "Add SSO Account" if you want to enable more ways to login to your Read account.
Accounts that you use to SSO with are associated with your Read account, such that if you join a meeting using one of these accounts (e.g. if you use your Microsoft account to join a Teams meeting), Read will be able to recognize and map your participant data from the call back to your Read account (e.g. for the deep dive and coaching metrics).
To learn more about using SSO with Read, see How does single sign-on (SSO) work with Read?