Skip to content

Clients

An organization can keep its clients apart inside it. This suits an agency: one login, one set of runners and one place to look, with each client’s work on its own. An organization without clients works exactly as before; clients are optional everywhere.

Owners and Admins add, rename and delete clients on the Clients page. Everyone picks what to look at with the client picker in the header: all clients, one client, or the organization’s own work. The choice is remembered per user and organization in that browser.

A connection, a job, a monitor, a store or a status page may have a client. Their runs, results and alerts follow: an alert from a client’s monitor is that client’s alert. When you move a monitor or job to another client, its runs, results and alerts move with it.

No client means the organization’s own. For a connection, no client means shared: every client’s work may use it, such as one Google service account added to every client’s Search Console property.

Work May use
A job or monitor of client A A’s connections and shared ones. Its destination must be A’s own.
A job or monitor with no client Shared connections only.
A sync of client A A’s own source and destination, never shared ones.

SREInsights checks this when you save, when a connection is moved to another client (refused while something couldn’t use it there), and again when a runner takes the run.

A job’s run knows its organization and client. By convention, a job writes under:

orgs/<org id>/clients/<client id>/ a client's job
orgs/<org id>/ the organization's own

Give each client a destination connection whose key may write under that client’s prefix only. On your own instance, sreinsights clients list prints the ids and prefixes (Operator commands).

On Team, a member below Admin can be limited to some clients. They then see and change only those clients’ connections (shared ones read-only), jobs, monitors, runs, results, rules, alerts and status pages, and can only create work for them. Owners and Admins always see every client.

Reports and deployments are organization-wide. Give a limited member a role without them if they mustn’t see those.

Routes and silences can match clientIds, by id, so renaming a client changes nothing. Notices carry the client’s name.

Deleting a client is refused (409 CLIENT_IN_USE) while it still owns connections, jobs, monitors, stores or status pages, or while a member is limited to it. Move or delete those first, or change those members’ clients on Team. This keeps a client’s rows from quietly becoming shared.

Set one up in Set up clients for an agency.