Orbit Schedule
What this page is — an orientation to Orbit Schedule: what a calendar is in this product, what a template does to it, and where the module ends.
What it is for — running the appointments an organisation actually keeps. Site visits, interviews, coordination meetings, content slots, and demo requests booked by members of the public.
The problem it solves — a generic calendar makes every event the same shape: a title, a time, some notes. A property viewing and a candidate interview are not the same shape. Schedule lets each calendar carry its own event form, so a site visit asks for the client's name and the unit they are interested in, while an interview asks for the round and a link to the CV.
Route: /org/orbits · Permission: View Orbits
1. The one idea that explains the rest
A calendar is created from a template, and the template decides what an event looks like.
| Set by the template | Set by you | |
|---|---|---|
| The fields on the event form | ✅ | — |
| The view a calendar opens in | ✅ | — |
| The colour events are drawn in | ✅ | — |
| The calendar's name and description | — | ✅ |
| Timezone, default duration, working days | — | ✅ |
| Who can be booked — the resources | — | ✅ |
| Whether the public can book it | — | ✅ |
Choose Site Visit Schedule and every event on that calendar asks for Client Name, Phone Number, Interested Unit/Plot, Visit Type and Cab Pickup Required?. Choose Candidate Interviews and the same calendar asks instead for Candidate Name, Position, Round and a Resume / CV Link.
Templates are maintained by the platform operator, not inside your organisation — see calendar templates.
2. What is in the module
| Area | Page |
|---|---|
| The list of your project's calendars | Calendar dashboard |
| Creating and configuring one | Create a calendar |
| Where the event form comes from | Calendar templates |
| Who can be booked | Calendar resources |
| Month, week, day and list | Calendar views |
| Adding and changing events | Create and edit an event |
| Inviting people | Event participants |
| Publishing a booking page | Share and embed |
| What the public sees | The public booking page |
| What arrives when someone books | What a booking creates |
| Invitation emails and WhatsApp | Event notifications |
| Every permission | Permissions |
| Integrating | API and webhooks |
3. Calendars belong to a project
Every calendar is scoped to one project. The dashboard lists the calendars of whichever project the project chip in the header has selected, and switching project switches the whole list.
The dashboard reads the project chip. A dashboard address that includes a project will still list the project the chip has selected, so a dashboard link shared with a colleague may open on their project rather than yours.
Send a link to the calendar itself, not to the dashboard — a calendar address opens the calendar it names, whatever the chip says.
4. Two audiences
Most of Schedule is for administrators. One part is not.
| Audience | Where | Signs in? |
|---|---|---|
| Administrators and staff | /org/orbits and the calendars under it | Yes |
| Members of the public | A calendar's public booking page | No |
A public booking page is off by default. It is switched on per calendar, and only calendars you explicitly publish are reachable.
5. Don't confuse this with…
| Working hours, holidays and leave | Those belong to Orbit People. Schedule's working days setting only decides which days a booking page offers |
| Contacts | Invitees are Orbit Pulse contacts. Schedule invites them; Pulse owns the contact record |
| Email and WhatsApp connections | A calendar chooses a connection; it does not create one. Connections are set up in Comm Channels |
| Scheduling blocks on a website | Page Builder's scheduling components embed booking into a public page. Schedule owns the calendar behind them |
| AI scheduling | There is none. A calendar resource can be an AI agent, which is a category of assignee — nothing schedules on your behalf |
6. Troubleshooting
See troubleshooting.