Connecting your calendar
The connection fails, your IT policy blocks it, or it succeeds but no meetings appear.
You're seeing: The calendar connection fails, your IT policy blocks it, or the connection reports success but no meetings appear in Revial.
Google Calendar
If you hit a "blocked" or "this app isn't verified" screen: This is your Google Workspace administrator's policy, not a Revial fault. Your admin needs to allow the Revial application for your domain. Send them the request — they will need Revial's application details, which we'll provide on request through your support channel.
Some organisations block third-party calendar access entirely. If that's the case, connect Outlook/Microsoft instead; Revial works the same way through either.
If the connection screen appears but you can't reach the "Advanced" or "Continue" option: Try again in a private browser window with only the relevant Google account signed in. Being signed into several Google accounts at once is the usual cause.
Microsoft / Outlook
Connection normally completes without admin involvement. If your tenant requires admin consent, the consent prompt will say so explicitly — forward that screen to your IT administrator.
Connected, but no meetings appear
1. Wait for the first sync. The initial sync is not instantaneous. Give it a few minutes before concluding it failed.
2. Compare against a colleague. If a colleague on the same settings can see tomorrow's meetings and you can't, this is an account-level issue and we need to look at it — go to the reporting section below.
3. Check which calendar you connected. If you have several calendars in the same account, meetings on a secondary calendar may not be included.
4. Check your internal/external rules. If Revial is set to external meetings only, internal meetings will not appear at all. See Revial didn't join the meeting.
5. If you disconnected and reconnected. Meetings synced under the previous connection may still be present. Disconnecting a calendar does not currently remove meetings that were already synced.
During onboarding
If several people are connecting calendars in the same session and some succeed while others don't, stop and note who failed rather than retrying repeatedly. The pattern of who succeeded tells us more than any individual error message.
If it still doesn't work
Send us:
- The affected user's email address and which provider
- A screenshot of the exact error or blocking screen
- Whether other users in the same organisation connected successfully
- Whether your organisation restricts third-party application access
Known limits
Calendar sync can fail silently for accounts with very large calendars or users who belong to several organisations. If your calendar is unusually large or you were recently migrated between organisations, mention it — those are known cases and we can check them directly.