# Connectivity

Your application connects to Cronofy once, and Cronofy connects to the
calendar services your users rely on. How your application obtains that
access depends on the level it works at:

- **Organization level**, with
[Organization Connect](https://docs.cronofy.com/developers/temporal-grid/connectivity/organization-connect/index.md).
Your application is authorized for a customer's Organizational Unit, and
gets its members, their calendars, and its scheduling configuration, such
as Selection Rules and Templates. This is what
[managed scheduling and rescheduling](https://docs.cronofy.com/developers/managed-scheduling/index.md)
builds on.

- **Service account level**, with
[Enterprise Connect](https://docs.cronofy.com/developers/temporal-grid/connectivity/enterprise-connect/index.md).
An administrator authorizes a Google Workspace, Microsoft 365, or Exchange
service account once, and your application gets access to the calendars
of the users and resources it covers, without each person authorizing.

- **User level**, with
[Individual Connect](https://docs.cronofy.com/developers/temporal-grid/connectivity/individual-connect/index.md).
Each person authorizes your application to access their own calendars.

These levels aren't alternatives for customers of different sizes. With
Organization Connect, and especially with
[Managed Organizational Units](https://docs.cronofy.com/developers/managed-scheduling/managed-organizational-units/index.md),
the members of the Organizational Unit still connect their calendars through
a service account or individually, behind the scenes. A large customer's
administrator can connect a service account once for everyone, while a
smaller customer's members each connect their own calendars. Your application
works with the Organizational Unit the same way in both cases.

Use Enterprise Connect or Individual Connect on their own only when your
application works at the calendar level and builds its own scheduling.

[Integration approaches](https://docs.cronofy.com/developers/temporal-grid/integration-approaches/index.md)
helps you choose between them, and
[Authorization & Authentication](https://docs.cronofy.com/developers/temporal-grid/integration-approaches/authorization/index.md)
explains the applications, accounts, and tokens they all share.


---
[Read in HTML](https://docs.cronofy.com/developers/temporal-grid/connectivity/)

## In this section

- [Organization Connect](https://docs.cronofy.com/developers/temporal-grid/connectivity/organization-connect/index.md) — Connect to your users' Cronofy accounts to allow API access.
- [Enterprise Connect](https://docs.cronofy.com/developers/temporal-grid/connectivity/enterprise-connect/index.md) — Working with corporate calendars at domain level to better satisfy enterprise security concerns and access resources for your application.
- [Individual Connect](https://docs.cronofy.com/developers/temporal-grid/connectivity/individual-connect/index.md) — How to obtain authorization from your users to access their calendars via the Cronofy API.