The BackOffice doesn't open to a single workspace. It opens to three — agent management, support and troubleshooting, permission configuration — each a separate starting point rather than a tab among others or a sidebar item with everything else visible at once.

The reason is operational, not cosmetic. The people using each section are in completely different headspaces. An admin editing how an agent collects documents should not, on the wrong click, land in a sync-failure triage view where every minute matters. A support operator scanning failed syncs shouldn't have agent configuration in their peripheral vision.

Above the three doors sits a glanceable summary — agent count, account count, sync health, API availability. You know the state of the system before you choose where to go.

The same chip bar runs the agents index and the support queue. The furniture stays, the nouns change. On agents: Type, Usage, Availability, Status, Category. On support: account ID, process, sync. An admin scanning one surface carries the mental model directly into the other — onboarding is halved, context switching is cheap.

A second question inside this decision: what happens to items that don't match. In early drafts they vanished. That broke the mental model for admins, who often come in looking for a specific agent whose status they've forgotten.

So unavailable agents stay on screen, dimmed, with a persistent activate action floating on hover. The filter reveals what's relevant; it doesn't hide what isn't.

The agents index is where every admin session starts. The decision that shapes it is what each card carries on its face. Every card shows account count and success rate without needing to be opened — so the operator can scan hundreds of agents and know which ones deserve a closer look, before committing to any of them.

At this scale, that's the difference between spotting the one agent that needs attention and having to open fifty detail pages to locate it. The operator's eye does the searching; the grid makes the searching cheap.

Open a support ticket and every sync shows two statuses side by side: did the sync process work, and did the delivery report land. They look related, but they can tell completely different stories — a sync can complete cleanly on our side while its webhook delivery fails on the client's side. Collapsing them into a single status pill hides exactly the information an operator needs to know where to look next.

At scale, most sync cycles return nothing new to download. That's not a problem — most users don't get a fresh bill every day. Treating nothing new as an error would flood the interface with false noise, so it's its own neutral state, the second most common state after success.

The drill-down places the re-launch button right next to the sync history, because the person reading a failure usually needs to act on it immediately.

The agent-detail screen is the busiest surface in the product. Admins drop into it when something looks off. In a few seconds they want: is the agent even on, how many accounts are syncing, what's the success rate, how is today looking, and where did the last failures cluster? I split the page into two zones.

On the left, a quiet stack of status and controls — the kind of figures you read by glancing down the margin of a book. On the right, the chart: failures are magenta, third-party errors are ochre, successes are the neutral tone. No legend is needed, because the colour vocabulary carries over from the status system — the same magenta that spikes here tags a failed sync card in the support queue.

CloudAgents ships in French, English, and European Portuguese. Any modal where localised agent content is authored — agent names, field labels that the end user will read — carries its own set of language tabs at the top.

The practical win: one click to flip between language versions of the same label, without leaving the modal, without losing your place. Admins often write the three versions in the same session — the tabs remove the penalty for doing so.

When this shipped, macOS didn't have Dark Mode yet — that came in 2018. iOS wouldn't get it until 2019. CloudAgents had both themes from day one, for two reasons.

One: SCA is a technical product. A dark surface is the right finish for something engineers and ops teams sit in front of.

Two: the people inside this product stare at status counters for long stretches. A dark, low-contrast surface is simply less tiring than a bright card on bright paper, six hours in.

Both themes existed from the start, in the same file, treated as equals. Neither is a colour inversion of the other — warm paper in light becomes cool graphite in dark, shadows lose their tint and become borders, cards drop their backgrounds and keep their outlines. Same vocabulary, different volume.