The calendar template catalogue
/admin/orbittemplates is not part of a customer organisation. It is gated on View Orbit Template
configuration, a platform-operator permission that a customer administrator cannot hold.
This page exists so that administrators know where templates come from, and so operators know what the screen does. If you are setting up a calendar, you want calendar templates instead.
What this page is — the catalogue of calendar templates every organisation creates calendars from.
What it is for — maintaining that catalogue: adding templates, editing their event schemas, and moving them between environments.
The problem it solves — every organisation needs a different event form. Rather than each building one, the platform ships a catalogue and organisations pick from it.
Route: /admin/orbittemplates · Permission: View Orbit Template configuration
1. What a customer administrator sees
The refusal names the category, the module and the permission required, so an administrator who follows a link here can tell immediately that it is not a screen for them.
2. What the catalogue holds
| Templates | The list an organisation chooses from when creating a calendar |
| Business functions | The groups templates are organised under — Marketing, Real Estate, HR & Recruitment, Healthcare Appointments and others |
| Event schema | The fields a template's events ask for, with their types, labels and required flags |
| Display configuration | The view a calendar opens in, and its event colour |
A template's event schema is the important part: it becomes the Additional Details section of every event on every calendar created from that template. See create and edit an event.
3. What an operator can do
| Action | Permission |
|---|---|
| View the catalogue | View Orbit Template configuration |
| Add a template | Create New Orbit Templates |
| Change one | Edit Orbit Calendar Templates |
| Activate or deactivate one | Activate or deactivate Orbit Templates |
| Import templates | Import Orbit templates |
| Export a template's configuration | Export orbit template configuration Json |
| Show it in the operator menu | Orbit Template Menu Listing |
Export and import move a template between environments as a file, so a template built in one can be promoted to another without re-entering it.
4. Deactivating a template
Deactivating removes a template from the picker for new calendars. Calendars already created from it keep working, and their events keep their fields — deactivation affects new choices only.
5. Changing a template that is in use
Editing a template's event schema changes the event form on every calendar created from it, including calendars that already hold events.
Events created before the change hold data against the old field. Removing a field from the schema stops it being displayed; renaming one means existing events no longer match it. Add fields freely; remove and rename with care, and check which organisations are using the template first.
6. Don't confuse this with…
| A calendar's settings | An organisation's own timezone, working days, resources and sharing. Nothing here |
| Custom fields in other modules | Those are per organisation. These are platform-wide |
7. Troubleshooting
| Symptom | Cause |
|---|---|
| Access Denied | Expected for anyone who is not a platform operator — §1 |
| A template is missing from an organisation's picker | It is deactivated |
| An organisation asks for a new field | The template must change, and the change affects every organisation using it — §5 |