Account and team setup

A few one-time steps that pay off the moment something breaks. The Get started checklist in the dashboard sidebar tracks them; dismissing it hides it for you only.

Open Sign-in & security from the menu under your name (bottom left) to add a passkey, set up an authenticator app, or manage your password. See Sign-in and security.

Invite your team

Open Settings → Users.
Click Invite user, enter their email, and pick a role (defaults to Member). Only a Super Admin can invite an Admin, Billing Admin or Super Admin. To invite a group, choose Invite several people and paste up to 25 addresses, one per line or separated by commas.
Invites expire after 14 days. Resend on a pending invite sends the link again and restarts the 14 days, even for an expired invite.

A pending invite uses a seat until it is accepted, expires or is canceled. See plans and limits for seats per plan. Teams managed by an identity provider can map groups to roles with SCIM.

Roles

Any Super Admin can change a role later from the Users table.

Super Admin: everything, including billing, role assignment, and SSO/SCIM. An account always keeps at least one: the last Super Admin cannot be demoted or deleted.
Admin: team and credential management (invites, API keys, integrations, the audit log) and deleting escalation policies, on-call schedules and services. Everything except billing, roles, SSO/SCIM and removing a Super Admin.
Billing Admin: everything a Member can do, plus billing (plans, payment methods, invoices). No team, credential or role management.
Member: full product access (monitors, incidents, dashboards), but no team, credential or billing management, and no deleting escalation policies, on-call schedules or services. Members see integrations with credentials masked. New users start here.
Auditor: read-only across the product, plus the audit log. For compliance reviewers.
Viewer: read-only, except acknowledging and resolving incidents. Viewers cannot read the audit log.

Every role can manage its own contact methods and notification rules.

Removing someone who is on call

Removing a user also removes them from every on-call rotation and escalation level they are in, and the people after them in a rotation move up. The dialog lists those rotations and levels and asks you to confirm with Remove anyway; through the API, repeat the DELETE with ?confirm=true. Afterwards, the readiness check shows any level that now pages nobody.

Set up your contact methods

A contact method is how you personally get paged: email, SMS, or a Slack DM. It is separate from a notification channel, which belongs to the account. Each user manages their own under Notifications → Contact methods in their personal settings, and admins can manage anyone’s.

Notification rules pick which contact method fires for high urgency (critical and major incidents) and low urgency (minor), with optional delays: for example SMS at 0 minutes, Slack DM at 5, email at 15. A new user starts with their sign-in email as a verified contact method, with a high and a low rule on it, so they are paged by email from day one.

See contact methods and notification rules.

Generate API keys

Anything you can do in the dashboard, you can do through the API.

Settings → API keys → New key.
Name it after where it will be used (local-dev, terraform-prod, ci). One key per use lets you rotate them independently.
Under Access, choose Ingest only for a key that only sends telemetry, or Full access for one that can also call the API. A full-access key can be limited under Scopes. To leave it unrestricted, tick Allow everything: it then reaches the whole customer API, including deleting monitors. Through the API, a full key with no scopes needs "full_access": true.
Click Create key and copy the value. It is displayed only once, so store it in your secrets manager.

Use a full-access key as a Bearer token:

curl https://api.siteqwality.com/http/jobs \
  -H "Authorization: Bearer <your API key>"

Keys belong to the account, not the user. Rotate mints a replacement with the same name, type, scopes and expiry, shown once, and lets you keep the current key working for an hour, 24 hours or 7 days while you deploy the new one (or stop it at once). Through the API:

curl -X POST https://api.siteqwality.com/v1/api-keys/$KEY_ID/roll \
  -H "Authorization: Bearer $SQ_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"overlap_hours": 24}'

overlap_hours is 0 to 168 (default 24); 0 ends the old key now. The response holds the new key, its secret and previous_expires_at, when the old key stops. A key already rolled can be rolled again once its successor is revoked. Rolling needs an account admin.

For long-lived automation, or automation a third party runs, use an M2M API client, which trades its secret for short-lived tokens.

Rate limits

Each API key, M2M client and connected app can make 600 requests a minute; the MCP server allows 300 a minute per key or user. Windows are whole clock minutes. Responses to these callers carry the limit and what is left of it:

RateLimit-Policy: "default";q=600;w=60
RateLimit: "default";r=412;t=23

r is the requests left in this minute and t the seconds until it resets. Over the limit, the API answers 429 with Retry-After in seconds. All API traffic also shares a limit of 100 requests a second, so spread bulk jobs out. Dashboard sessions have no per-minute limit.

Export your configuration

GET /v1/export returns what your account has configured as one JSON document: HTTP, TCP and ping monitors, heartbeat monitors, browser checks, DNS record monitors, notification groups and channels, integrations, alert sources, services, and escalation policies with their levels. Each list holds the same items as its /v1 list, without secrets. Keep it as a backup or compare two exports to see what changed.

curl https://api.siteqwality.com/v1/export \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" > siteqwality-export.json

The document starts with version (1) and exported_at. A key limited to scopes needs read:monitors, read:notifications and read:incidents. Status pages are not in the export yet.

Configure billing

Super Admins and Billing Admins manage billing on Settings → Billing: change plans (upgrades apply immediately, downgrades at the end of the billing cycle), manage payment methods, download invoices, or cancel at the end of the period. See plans and limits for what each plan includes and what happens when a plan ends or a payment fails.

Connect integrations

Connect the chat tools and webhooks you use under Manage → Integrations before you point monitors at them. See Integrations.

What’s next

Concepts and glossary The vocabulary used across the docs.

On-call schedules Stop manually paging the same person every night.

Notification rules How personal contact methods, urgency, and delays interact.