Quickstart

Schedule-X Cloud has two quickstart paths. Both use the same secure frontend-session flow, but calendar provisioning is different depending on whether your users connect an external calendar provider.

Choose Your Setup

Without Calendar Sync

Choose this path when Schedule-X Cloud will store native calendars and events without connecting Google Calendar. Your backend provisions the calendars that members of your organization can use.

Open the quickstart without calendar sync →

With Calendar Sync

Choose this path when each signed-in user will connect Google Calendar. Schedule-X Cloud creates linked calendars from the provider account, imports events, and keeps changes synchronized in both directions.

Open the quickstart with calendar sync →

What Both Setups Share

Your backend authenticates the user and calls createFrontendSession() with the stable user ID from your own application. The first call creates the Schedule-X Cloud user and Member membership; later calls update the user’s profile and issue a fresh one-hour frontend token.

Implementers do not need to create or store a separate Schedule-X Cloud user ID. The browser receives only the short-lived frontend token. Your organization API token remains on your backend in both setups.

For the credential boundary in more detail, see Auth Flow.