Set up clients for an agency
An agency usually wants one login, one set of runners and one place to look, with each client’s work kept apart. In SREInsights that is one organization with clients. This guide sets up two clients, Acme and Globex.
You need: an Owner or Admin role.
1. Add the clients
Section titled “1. Add the clients”Clients → New client, name it Acme, and Add client. Repeat for Globex.
The client picker in the header now offers All clients, each client, and the organization’s own work. Lists, the Overview and Alerts follow the picker.
2. Decide what is shared
Section titled “2. Decide what is shared”| Connection | Shared or a client’s own? |
|---|---|
| A Google service account added to every client’s Search Console property | Shared (no client) |
| A client’s Shopify store, database, or API credentials | The client’s own |
| A job’s S3 destination | Always the client’s own: a client’s job may only write to that client’s destination |
| Notification channels | Organization-wide; route by client instead (step 6) |
When you add a connection, set its Client, or leave it empty for shared.
3. Give each client its own destination
Section titled “3. Give each client its own destination”A client’s jobs write under orgs/<org id>/clients/<client id>/. For each client, create an access key in AWS that may write under that prefix only, and add an S3 destination connection for the client with that prefix.
On your own instance, sreinsights clients list --org <org slug> prints the organization’s id and each client’s id and prefix (Operator commands).
4. Create the clients’ monitors and jobs
Section titled “4. Create the clients’ monitors and jobs”In each monitor and job form, set Client to the client. The form offers only that client’s connections and the shared ones. A monitor or job with no client is the organization’s own and may use shared connections only.
Runs, results and alerts take their monitor’s or job’s client. Move a monitor to another client later and its history moves with it.
5. Give each client a status page
Section titled “5. Give each client a status page”Status pages → New status page, set Client, and add that client’s monitors and jobs. Only members who see that client see the page. To show it to the client themselves, share it by link.
6. Route alerts by client
Section titled “6. Route alerts by client”Alerts carry their client, and every notice names it. To send each client’s alerts to its own channel, create routes that match the client. The routes editor matches severity and labels; to match by client, use the API’s clientIds:
curl -X PUT https://console.sreinsights.com/api/v1/notification-policy \ -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \ -d '{ "routes": [ { "name": "Acme", "match": { "clientIds": ["<acme client id>"] }, "channels": ["<acme channel id>"], "continue": true }, { "name": "Everyone", "match": {}, "channels": ["<agency channel id>"] } ] }'PUT replaces the whole list, so send every route. Silences can match clientIds too.
7. Limit team members to their clients
Section titled “7. Limit team members to their clients”On Team, set a member’s Clients column (for members below Admin). A member limited to Acme:
- sees and changes only Acme’s connections (and shared ones, read-only), monitors, jobs, runs, rules, alerts and status pages,
- can create work only for Acme.
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.
Removing a client
Section titled “Removing a client”Deleting a client is refused while it owns connections, jobs, monitors, stores or status pages, or a member is limited to it. Move or delete those first.
More: Clients.