Organizations and roles
An organization holds your runners, connections, monitors, jobs, rules, alerts, channels and status pages. Nothing is shared between organizations: each one’s data is kept apart in the database by row-level security, and its connection secrets are encrypted under its own key.
Creating an organization
Section titled “Creating an organization”Signing up creates a user and an organization, and makes you its Owner. You can belong to several organizations: someone adds you from their Team page.
The Organizations page lists every organization you belong to and how each is doing right now (firing alerts, failing monitors, runners online). Select Switch to to work in another one.
Every member has one role in each organization. A role decides which pages the member sees and what they may change. Pages a role can’t use are left out of the sidebar.
| Role | Can do |
|---|---|
| Owner | Everything, including changing the organization’s own details. |
| Admin | Everything an Owner can, except change the organization itself. Manages members, clients, runners, connections, channels and routes. |
| Operator | Creates and changes monitors, jobs, alert rules, silences, status pages, reports and deployments. Acknowledges and resolves alerts. Sees runners, connections and channels without changing them. |
| Responder | Acknowledges and resolves alerts, creates silences and updates deployments. Sees monitors, jobs, rules, status pages and reports without changing them. |
| Viewer | Sees everything a Responder sees. Changes nothing. |
Only Owners and Admins:
- add, change and remove members, and limit them to clients,
- create runner groups and registration tokens, and disable runners,
- add and change connections (everyone else sees that they exist, never their secrets),
- add channels and edit routes,
- add, rename and delete clients,
- turn a status page’s share link on or off,
- connect stores on the Stores page.
Members and invitations
Section titled “Members and invitations”On Team, select Add member, enter an email and choose a role.
- If the person already has an SREInsights account, they are added at once.
- Otherwise SREInsights gives you a one-time link to
/join?token=…. Send it to them yourself: SREInsights sends no email for invitations. The link works once. Unused links are listed under Invitations, where you can withdraw them.
You can change a member’s role or remove them. An organization always keeps at least one Owner.
Limiting a member to clients
Section titled “Limiting a member to clients”If your organization has clients, the Clients column on Team limits a member below Admin to some of them. A limited member sees and changes only those clients’ connections (and the shared ones, read-only), jobs, monitors, runs, results, rules, alerts and status pages, and can create work only for those clients. Owners and Admins always see every client.
Reports and deployments belong to the whole organization. If a limited member must not see them, give them a role without them.
Passwords
Section titled “Passwords”- Change your own with Change password in the sidebar. Your other devices are signed out.
- Reset someone else’s. An Owner or Admin can create a one-time reset link for a member on Team. It opens
/reset?token=…, works for 24 hours, and can’t be made for someone with a higher role than yours. SREInsights sends no email; pass the link on yourself.
Deleting your account
Section titled “Deleting your account”In the SREInsights mobile app, go to Account, then Delete account. The public page /account-deletion on your SREInsights URL describes the other ways.
An organization has a plan. Plans set limits on hosted runners: how many monitors and jobs may run on them, and the shortest schedule interval there. A save that would go over a limit is refused with 403 PLAN_LIMIT. Monitors and jobs on your own runners have no such count or interval limit beyond the 30-second floor.