Sometimes, people accidentally create multiple different Read accounts without realizing it, which leads to Read not working as expected. This usually happens when using SSO (e.g. Google or Microsoft) to sign in, as the SSO account that you pick may not be associated with the original Read account you created.
For example, you may have created a Read account through Zoom SSO when you installed Read's Zoom app, and then later when you received an email to view a report on Read, you tried logging in with Google SSO, creating a new account in the process.
To confirm this:
-
Search your emails for a "Welcome to Read!" email from Read.
-
Look at the address on the "To:" line; you've created an account under this address.
- Make sure to search across all of your accounts to find them all.
To resolve this, we recommend you:
- Decide which account you want to keep using going forward.
- This could be whichever account already owns most of your meetings, whichever account has a paid subscription, or something else; it's up to you.
- Keep in mind that you can always change the calendars that are connected and even the primary email address on your account later, if this is something you're considering.
-
Log in to the account(s) that you don't want to keep using the correct SSO provider/email address.
- You can then either delete the account entirely, or disconnect all calendars.
- If you choose to delete the account:
- Go to the bottom of your Account Settings, hit the "Delete my account" button and confirm.
- Please be aware that this will delete any meetings owned by this account, so you may want to download those meeting reports to your computer first.
-
If you choose to disconnect all calendars:
-
Go to your Account Settings > Calendar and click "Disconnect" for any connected calendars.
- This will stop Read from automatically joining any future meetings for this account.
- Note that meetings may still get shared with this account if the primary email address on it is invited to future meetings, but no meetings will be owned by this account going forward
-
Comments
0 comments
Article is closed for comments.