Administration overview
Everything in Administration needs booking:admin. It configures how the business behaves; nothing here changes which code runs — the product is configuration, not customisation.
| Page | What it controls |
|---|---|
| Business Profile | Who the business is, its default rules, the setup checklist and business templates |
| Booking Page | The public page customers book on and the code that puts it on your website |
| Configuration | Features, terminology, booking rules and tenant settings |
| Custom fields and documents | Extra questions on records, and the customer document types |
| Workflow | Your own status names over the fixed booking lifecycle |
| Role Permissions | Which role holds which permission |
| Account & API | Plan and usage, API keys and webhooks |
| Outbox Events | Emails queued for delivery |
Three rules this module follows
- Templates are starting points. Applying a business template unpacks ordinary features, terminology and settings, and is then forgotten. Nothing branches on the business type.
- Features have two gates. Available on your plan is a billing fact; switched on by you is a preference. They are shown separately so the screen can say "upgrade your plan" and "switch it on" as the different problems they are.
- Terminology is labels only. Renaming Customer to Patient changes the words, never a route, field or integration name.