# Connect your first calendar

A safe first connection, from provider sign-in to checking access.

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

## Before you begin

Use an account you are authorized to connect. For a first test, create a separate test calendar at your provider. Do not use customer data for a trial workflow. Check [provider support](https://docs.getridian.com/integrations/providers/) and, for a work account, your organization's rules.

## Connect and verify

1. Sign in to the [Ridian console](https://console.getridian.com/) and select the intended workspace.
2. Open calendar connections and add the provider. Google and Microsoft use their sign-in and consent pages. iCloud/CalDAV use the provider's required credentials; iCloud needs an app-specific password.
3. Review the permissions requested by the provider. A successful login does not necessarily grant every calendar or action.
4. Return to Ridian and check the account status and calendar list. Confirm which calendar is your test calendar and whether it is writable.
5. Choose what to do next: [create a sync](https://docs.getridian.com/guides/sync/) or [connect an assistant](https://docs.getridian.com/guides/assistants/). These are separate access decisions.

## Check the result

You should see the intended account and accessible calendars. If a shared calendar is missing, check the account used for sign-in and the provider's sharing permissions. A calendar shown as read-only cannot become writable through a Ridian checkbox.

## If the connection fails

Check whether the provider consent was completed, your organization permits the connection and the password is correct. For an existing broken connection, use [reconnect](https://docs.getridian.com/guides/reconnect/) rather than creating duplicates. Share the provider, time and error with support; never send passwords or access tokens.