Account and team setup

Once you have an account, there are a handful of one-time setup steps that pay off the moment something breaks. Do them now, not at 3am.

Invite your team

1. Open Account → Users.

2. Click Invite User, enter their email, and pick the role they’ll join with (defaults to Member). Inviting someone as Admin, Billing Admin, or Super Admin requires you to be a Super Admin yourself. To invite a group, choose Invite several people and paste up to 25 addresses (one per line, or separated by commas).

3. Invites expire after 14 days. Pending invites stay listed in the same table with Resend and Cancel actions: Resend re-sends the original link and resets the expiry clock (including for already-expired invites); cancelling kills the link.

4. Roles, changeable later by any Super Admin from the dropdown in the Users table:

   • Super Admin: everything, including billing, role assignment, and SSO/SCIM. Multiple people can hold it. The account’s original user is always a Super Admin and cannot be demoted or deleted.
   • Admin: team and credential management (invites, API keys, the audit log), everything except billing, roles, and SSO/SCIM.
   • Member: full product access (monitors, incidents, dashboards), but no team, credential, or billing management. New users start here.
   • Auditor: read-only across the product, plus access to the audit log. For compliance reviewers who should see everything and touch nothing.
   • Viewer: read-only. The one exception: a viewer who is on call can still acknowledge and resolve incidents. Viewers cannot read the audit log.

Caution

Pending invites count toward your plan’s seat limit immediately, not on acceptance. Expired invites stop counting on their own, and cancelling frees the seat right away. Free accounts have 3 seats.

Directory-managed teams should map IdP groups to the exact role IDs in SCIM role mapping. Unknown names become Member. The account’s original user cannot be deprovisioned.

Set up your contact methods

A contact method is how you personally can be reached, whether that’s your email, your phone for SMS, your phone for calls, or your Slack DM. Distinct from a notification channel, which is account-level.

Each user manages their own contact methods under Account → Contact Methods. Available types:

Type	What it is
email	Your inbox. Always pre-populated with your sign-up address.
sms	A verified phone number. SiteQwality sends a verification code on add.
phone_call	The same verified number, dialed instead of SMS-ed for high-urgency pages.
slack_dm	DM via the Slack integration once your account has connected it.

Once contact methods exist, set up notification rules to define which method fires for which urgency:

• High urgency: incidents from monitors, escalation pages, anything that should wake you up.
• Low urgency: informational, status-only.

A rule has an urgency, a contact method, and an optional delay_minutes. Stack multiple rules at increasing delays for personal escalation: SMS at 0 min, phone call at 5 min, email at 15 min.

See the Notification rules how-to for the full setup.

Generate API keys

Anything you can do in the dashboard, you can do via the API. Generate a key under Account → API Keys.

1. Account → API Keys → Create key.

2. Name it after where it’ll be used (local-dev, terraform-prod, ci). One key per use case so you can rotate them independently.

3. Copy the value when shown. It’s only displayed once, so store it in your secrets manager.

4. Use it as a Bearer token:

   curl https://api.siteqwality.com/http/jobs \
     -H "Authorization: Bearer sq_live_..."

Keys are scoped to the account, not the user. Revoke immediately if leaked.

Tip

An API key can do everything the account can. For automation that should be limited to specific resources, or that a third party operates, use an M2M API client instead: scoped permissions, short-lived tokens, built-in rotation, and immediate revocation.

Whichever you use, every change either one makes is recorded in the audit log.

Configure billing

1. Settings → Billing → Plans to see what you’re on and what’s available.

2. Change plan flips you between tiers. Upgrades are immediate; downgrades take effect at the end of the current billing cycle.

3. Customer portal opens the Stripe-hosted portal where you can update payment methods, download invoices, and cancel.

Usage-relevant counters (monitor count, ingested logs/metrics/traces volume, RUM session count) live under Settings → Billing → Usage. Hard limits are enforced at the API layer, so you’ll get a 403 Forbidden if a request would push you over.

Set up integrations early

The rest of these docs assume Slack/Teams/Discord/Telegram/webhook integrations are already connected if you reference them. Connect the ones you use under Settings → Integrations before you wire monitors to them. See Integrations overview for the per-tool setup steps.

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.