Page unavailable? Copy its Markdown and paste it into your chat.
One platform, three ways in
Understand Personal, Business and Infrastructure, and how the Ridian suite fits together.
Reviewed · 2026-09-20 / Ridian
Personal: your calendars and assistants
Section titled “Personal: your calendars and assistants”Connect accounts you own, synchronize selected calendars and choose what an assistant may see or change. An account can contain several calendars; connecting the account is different from granting access to every calendar.
Business: shared boundaries
Section titled “Business: shared boundaries”A workspace brings membership, roles and organizational policy together. The organization sets a ceiling; a member’s own choices can narrow access further. Paying for a workspace does not transfer ownership of a member’s personal calendar account to its administrator.
Infrastructure: calendar access for software
Section titled “Infrastructure: calendar access for software”Ridian provides an OAuth-based MCP endpoint and a REST read interface. They reuse the same permission boundary. The broader partner platform—project management, expanded REST writes and partner webhooks—is being developed separately. These are not all available merely because MCP supports related actions.
How the pieces connect
Section titled “How the pieces connect”Provider account → selected calendars → effective permissions → sync or authorized client
Sync creates and maintains copies according to a connection’s rules. Live assistant queries ask the provider for the requested window. A sync copy and a live query have different lifecycles; see sync behavior and permissions.
Choose your next step
Section titled “Choose your next step”Use the capability guide for provider and channel distinctions, workspace setup for teams, or the developer overview for an integration. Commercial terms are agreed separately; this documentation is not a pricing offer.