Integration lanes
5Dash, Admin, Inbound, Engine, manual
Calendly replacement build
One booking layer for every Atlas tool.
This app is the deployable calendar surface. The contract lives in shared code, records live in the Atlas Supabase project, and every source app stamps its origin.
Shared auth boundary
Uses the Atlas Supabase session family and `.atlasdash.co.za` cookie domain when deployed.
Providers
2Google and Microsoft first
Target domain
calendarcalendar.atlasdash.co.za
Timezone
SASTAfrica/Johannesburg
Integration map
Connected Atlas surfaces
Atlas Dash
Project, client portal, and employee views link to bookings without owning scheduling logic.
Atlas Inbound
Deals and lead handovers can create booking intents and attach meeting prep records.
Atlas Engine
Agents can queue reminders, meeting briefs, and availability checks through one service boundary.
Calendar Ops
Atlas staff get a daily operating desk for availability, provider health, and review queues.