Google and Microsoft

Calendar access

Choose Connect calendar, pick Google or Microsoft and tick what Ridian may use: calendar is always included, tasks are preselected, contacts and sending email are optional. The provider’s consent screen then asks only for those areas. Select the intended provider account there. If you decline an area on that screen, the account still connects with calendar access, and Ridian tells you what is missing; add it later with Add access on the account under Connections. Rooms have their own Rooms tab. Existing shared access depends on permissions at Google or Microsoft; Ridian cannot manufacture rights the provider has not granted.

Alvin and MCP use the same provider cores for reading, availability, supported standalone writes and bounded weekly-series creation. Weekly series without guests have one weekday, an interval in weeks and 2–104 occurrences within 104 weeks. Single occurrences of your own series without guests can be changed, moved or deleted, and entire series renamed. Use the calendar app for daily, monthly, yearly or custom recurrence, schedule changes and deleting entire series. The recurrence overview distinguishes this scope from calendar sync.

Microsoft: approval by your IT

Some organisations only let administrators approve new apps. Microsoft then shows an approval notice instead of the consent screen, and Ridian tells you that your IT needs to approve it. Ask your Microsoft 365 administrator to approve Ridian in the Microsoft Entra admin center (Enterprise applications, admin consent), then connect again. Until then you can add a calendar as a read-only ICS feed.

Microsoft partial consent

A Microsoft connection can succeed while an optional permission is missing. Check the specific account capability when tasks, contacts, mail or shared calendar access fails. Reconnect or request the appropriate scope upgrade through Ridian. A tenant administrator’s restrictions may require their involvement.

Tenant binding is a separate boundary from signing in successfully. Do not connect a different organization’s account as a workaround for a denied work-account policy.

Google organizational resources

Google Workspace room discovery requires organizational setup in addition to an ordinary connected calendar account. Personal Google accounts are not a substitute for a Workspace resource configuration. See rooms.

Additional domains

Tasks, personal contacts and sending mail require their own scopes and client permissions. For Google contacts, only your own contacts are required; “Other contacts” and the Workspace directory are optional on the consent screen, and searches in those sources skip accounts without them. To add them later, grant Contacts again for that account. Calendar permission is not a blanket authorization for these domains. Gmail support here is sending mail, not reading an inbox. Check tasks, contacts and mail before enabling a workflow.