Monitoring
Client roster view
Every client account on one screen, ordered by what needs you first, without a client identifier in the URL.
An agency running experimentation across many client sites has a search problem before it has a statistics problem. The roster view is the answer to it: every client, every website under them, how many experiments are running, and how many signals are unresolved at each severity.
The scope comes from the signed-in session rather than from the address. An earlier design took a client identifier in the path and checked it against the caller company, which works but puts a tenant identifier in the URL purely so it can be defended. Deriving the scope from the session removes that surface: there is no identifier to tamper with.
The two shapes it takes match how the product is actually structured. An agency sees its client roster, not itself, because an agency company holds the team while its clients hold the websites. Anyone else sees their own account, so the same screen is useful to a direct customer rather than being an agency-only feature.
One deliberate absence: platform administrators get no global view here. Their elevated access is right for authorisation and wrong for an overview, where it would render every company on the platform.