# Your calendars. One connected layer.

Connect calendars, control access, and build on Ridian. Find the right path for the way you work.

Source: https://docs.getridian.com/
Language: en
Reviewed: 2026-09-20

## Understand the building blocks

**Connections** bring your existing calendar accounts into Ridian. **Sync** keeps selected calendars aligned. **Assistant access** lets an authorized AI client read or act within your rules. **Workspaces** give teams a common policy boundary. **Developer interfaces** expose supported operations to applications.

Your calendar provider remains the home of your events. Ridian coordinates access and synchronization across those providers. You do not need to move your calendar to a new calendar application.

## Start with a real outcome

- [Connect your first calendar](https://docs.getridian.com/guides/first-calendar/) and check the calendars it exposes.
- [Use ChatGPT or Claude](https://docs.getridian.com/guides/assistants/) with a deliberately small permission set.
- [Set team boundaries](https://docs.getridian.com/admin/workspaces/) before inviting colleagues.
- [Explore the developer interfaces](https://docs.getridian.com/developers/) and their current scope.

## Know what is available

Ridian is in beta. Capabilities differ by provider, permission and access channel. Check the [capability guide](https://docs.getridian.com/product/capabilities/) before designing a workflow. Pilot features need a scoped setup; planned features are not available yet.