# Managed scheduling and rescheduling

Hand the full scheduling lifecycle to Cronofy: finding times, booking,
rescheduling and cancelling. Embed Cronofy's scheduling in your product, or
build your own interface and let Cronofy run underneath.

Cronofy tells your application what happens to each Scheduling Request with
[webhooks](https://docs.cronofy.com/developers/temporal-grid/webhooks/index.md), so it can
keep its records up to date and drive its own workflows.

AI agents can schedule on your users' behalf through the
[MCP Server](https://docs.cronofy.com/developers/temporal-grid/mcp-server/index.md).


---
[Read in HTML](https://docs.cronofy.com/developers/managed-scheduling/)

## In this section

- [Authorization](https://docs.cronofy.com/developers/managed-scheduling/authorization/index.md) — Which authorization methods apply to managed scheduling, and when to use each.
- [Managed Organizational Units](https://docs.cronofy.com/developers/managed-scheduling/managed-organizational-units/index.md) — Provision an Organizational Unit for each of your customers, so your application can run managed scheduling for them without an authorization flow.
- [Scheduling Requests](https://docs.cronofy.com/developers/managed-scheduling/scheduling-requests/index.md) — The model behind managed scheduling, and the embedded and headless ways to work with it.