Calendars
A calendar service holds as many named calendars as you need — one per person, room or resource — and a booking page points at one of them.
View as MarkdownA calendar service is a container, not a single calendar. Add as many named calendars inside it as you need — one per person, room or resource — and point each booking page at the right one.
Making one
- 1Add the serviceProject → Add service → Calendar. One is usually enough for a whole business.
- 2Name a calendarInside the service, create a calendar per person or resource — "Alexander", "Consult room 2", "Van 3".
- 3Point a booking page at itOn the booking page, Calendar it books into binds the bookings. A host can also carry its own calendar, so round-robin lands on the right person's.
From an AI
Over MCP: create_service with type: "calendar", then create_calendar per person, and list_calendars to read the ids back. Pointing a non-calendar service id at create_calendar is refused by type.
One calendar per human
Round-robin only reads as fair if each host owns a calendar. Sharing one calendar between two people makes both look busy whenever either is.