Settings, people, domains and tokens
The administrative half of the console, rebuilt screen by screen.
The administrative half of the console, rebuilt screen by screen.
The screens an operations lead lives in, and nobody else thinks about until they are wrong.
**People.** Invite by email rather than creating an account and passing a password along. Each person's page shows exactly what they can do, and the same set is editable on their form — so the answer to "why can Sam not see the runs" is one screen rather than a support request.
**Booking preferences** are now a builder beside a live preview. Opening hours decide which slots a customer is offered, which means a mistake here is a customer booking a bay that is not staffed. Seeing the effect before saving is the whole point.
**Sending domains** tell you which record is wrong rather than that something is. See [the September release](/changelog/inbox-keeps-itself-up-to-date/) for the retry behaviour that finished this off.
**API tokens** show their scopes at a glance, so a token that can do more than it needs to is visible rather than inferred.
### Two repairs
Opening hours are read back exactly as they were saved — they were being interpreted differently on write and read, which is as bad as it sounds for a setting that governs bookings.
The dark theme had colours missing on a few screens, leaving text that was technically present and practically unreadable.
Talk to us
Tell us your branches, your channels, and roughly how many customers come due each month. If it is not a fit, we will say so.
One business dayOne person, one email. No sequence, no drip, and no calendar link to negotiate with.