The admin workspace

The admin workspace is at /admin. A slim sidebar down the left carries the map of the product; a topbar across the top carries everything about this session — search, alerts, the light/dark switch, and who is signed in.

Where everything livesCopy Anchor Link

Dashboard sits above the groups, because it belongs to no one job. Below it the sidebar is grouped in the order a business runs: do the work, look after customers, collect the money, bring in more, look back.

Settings and Documentation are pinned in the sidebar's foot. Settings opens on a list of topics in groups — Business, Booking, Money, Crew, Messages, Connections — with a search box on top; each topic is its own page with a Back to Settings. The one sidebar "Settings" link stays lit on every page in it, including API keys, Webhooks and Calendar feeds.

Every page is also reachable by name from the command palette: press ⌘K (Ctrl+K on Windows) and type. The palette knows the old names too, so searching "catalog" finds Services and "developers" finds API keys.

Reading the dashboardCopy Anchor Link

The dashboard opens with a greeting and today's date, then reads top to bottom as one morning: a setup warning while a required step is still open, what needs deciding, then the shape of the day, then the figures the day adds up to, then the week, then the health checks.

Needs a decisionCopy Anchor Link

One ranked list of everything today wants an answer about, most urgent first, grouped under four bands. Each band is headed by its own icon, its name, and how many rows are in it:

• Clock disagrees — a job whose clock and status disagree: a late start, a visit running over, or one never closed out.
• Without crew — an upcoming job nobody has accepted.
• To collect — completed work with money outstanding, with the amount.
• Away from the address — a clock-in recorded away from the customer's address in the last seven days.

Every row reads in the same four columns: the day and hour of the job, who it is for, the street and town it is at, and — in the To collect band — what is still owed. The band's name says what its rows have in common, so a row adds only what it does not share with the rest of its group — a job with some of its crew accepted, a part-payment, a card with a hold on it that was never charged. Each row carries one action. Assign opens the booking at its Crew card, Charge at its Payment card, Review at its timeline. Nothing is closed out or completed for you.

Only five rows of a band are shown. When there are more, that band says so — "Showing 5 of 25" — with a link to the full list. When every band is empty the whole list becomes one line, "You're clear for today"; what it checked is in the info tip beside the list's heading.

Today's boardCopy Anchor Link

The day itself, drawn left to right across the hours it actually spans. One row per rostered crew member or team, that crew's rostered stretches as a track, each accepted job as a block the width of its own duration, hour gridlines, and a line marking now.

Each lane carries the crew's name and, under it, the hours they are rostered for that day — or On time off today / Not rostered today when there are none.

A block carries its start time, job code and customer, and states its day-of status — Not started, En route, In progress, Completed, No-show — or the exception that has taken it over. A team gets a lane of its own with its members listed beside the name; its rostered hours are the overlap of its members' hours, less any approved time off.

Jobs nobody has accepted are not drawn on the board: they are listed once, in the Without crew band of Needs a decision above it.

On a phone the board is a list instead: today's jobs grouped under each crew member, each opening its booking.

Lanes with work sort above lanes without; a rostered crew with nothing booked is an empty track under their name, and crew with neither hours nor work today collapse to one line of names beneath. The board is rendered on the server, so it states the clock it is accurate as of — reload for a fresh now-line.

The figuresCopy Anchor Link

Readings, below the work rather than above it — the day and the week first:

A cancelled job counts nowhere; everything else counts, no-shows included. A figure that is zero is left out — Booked today appears with the day's first sale — and with no figures to show the card is not drawn.

Then two about your customers, drawn only when there is something in them:

Every figure carries an "About …" info tip with the full rule and a link to the list behind it. Below them, This week charts the same seven days.

AutomationCopy Anchor Link

A card at the foot of the page, about the machine rather than the work: whether the automation tick is running, and when it last ran. Crew paperwork is not here — a credential expiring never stops anyone being offered, assigned or dispatched work, so it is worked on the Crew page, where it lives.

Getting startedCopy Anchor Link

A new company gets a setup checklist at /admin/getting-started, with the sidebar counting the steps left ("Getting started · 5 of 7") until the required ones are done. The dashboard carries no checklist: while booking rules or payments are still open it shows one warning line each, naming what you are living with until the step is done and linking straight to it. You can dismiss the checklist, which clears both the sidebar count and those lines, and restore it from the Getting started page.

That page opens with Your booking link in a copyable field — the link of your first enabled booking form, which is the one to put on a business card, in a signature, or in a social profile.

An address that reaches nothingCopy Anchor Link

A mistyped address, a stale bookmark, or a link to something since renamed lands on one page that says so. It shows the address as it was typed — so a link read over the phone can be checked character by character — and one button back into the part of Grout you were already in: the dashboard from anywhere under /admin, the crew portal from /crew, your account from /account, these pages from /docs.