Skip to content
Accessde

Ridian help

Updated: 2026-09-20

Find Ridian’s current capabilities and how to get started. Access also depends on your plan, calendar permissions and workspace settings.

Getting started

  1. Sign in to Ridian and select your workspace.
  2. Connect your calendar account and check the calendars shown.
  3. For sync: choose a source, destination, direction and which details to share.
  4. For an AI assistant: connect the Ridian connector provided to you. Permit only the accounts, calendars and actions you need.

Set up iCloud and other CalDAV calendars →

Current capabilities

Calendar sync

Available in beta
Google, Microsoft, CalDAV and ICS feed sources; writable calendars as destinations. One-way and two-way connections depend on the plan. ICS feeds are read-only.

Google and Microsoft in AI connectors

Available in beta
Read events, find available times, and create, update or delete standalone events without guests. Calendar and assistant permissions limit every request.

CalDAV in AI connectors

Not released yet
After release: read events and availability, and create, update or delete standalone events without guests. Not yet available.

Weekly series via AI

Available in beta
Create bounded weekly series for Google and Microsoft. Edit or delete series in the calendar app. CalDAV series creation is not supported.

Permissions and visibility

Available in beta
Choose permitted accounts and calendars, separate read/write permissions, and share busy times, titles and times, or permitted details. Revocation and reconnect have been tested.

Tasks, contacts and outgoing email

Available in beta
Separate Google/Microsoft permissions are required. Email is send-only; no mailbox reading. Not available through CalDAV.

Respond to invitations

Available in beta
Google and Microsoft: accept, tentatively accept or decline when the event supports it and the connector has separate permission. The AI action does not send a response email to the organizer. Not supported for CalDAV.

Create Google calendars

Available in beta
With separate permission, the AI connector can create Google secondary calendars. This is not general management or deletion of arbitrary calendars; the assistant may additionally block destructive actions.

Find and book rooms via AI

Pilot / on request
Availability depends on workspace settings, provider permissions and room access. Booking sends an invitation through the provider; requested does not mean confirmed by the room. A read-only room source does not enable booking.

Microsoft room calendar sources

Pilot / on request
Read-only pilot access after enablement. Currently about a five-minute polling interval plus processing. This source does not resolve issues with booking replies or email aliases.

Hosted Exchange via EWS

Pilot / on request
Available through a supported pilot. Access depends on your Hosted Exchange provider and individual enablement.

External sharing through a recipient invitation

Not available yet
The Kalender Sync flow in which an external recipient selects their own destination calendar is not yet available. Workspace invitations are a separate feature.

Plans and billing

Pilot / on request
Plans and seats are set up manually for contract customers. Free pilots follow the agreed terms. Self-service checkout and subscription management are not yet available.

You control access

Your calendar provider’s permissions and your assistant’s permissions are separate settings. Provider write access alone does not permit an assistant to make changes. With busy-only visibility, the assistant receives no event titles or descriptions. Ridian may still read calendar data from the provider to process the request.

You can revoke assistant access in Ridian. This is separate from removing a calendar connection: before removing one, check which syncs use that account.

If something goes wrong

First check the connection in Ridian, selected calendars and assistant permissions. A provider error does not mean a calendar is free. If tools are missing from your assistant, reconnecting and starting a new chat may help; this does not replace missing permissions.

Send support the provider, time with timezone, and error message. Do not include passwords, access tokens or private event descriptions. Contact