Organizations and teams
Share monitors, run history, and CI keys with colleagues—one organization per GitHub account, with optional per-monitor access controls.
On this page
Overview
Every signed-in user belongs to exactly one organization. On first sign-in, Signal Diff creates a personal organization with you as the Owner. Invite colleagues by GitHub username to share the same dashboard, run history, schedules, and (on paid plans) CI API keys.
- One org per person — A GitHub account can belong to only one organization at a time. Someone already in another org must leave it before accepting your invite.
- No per-seat pricing — Organizations are included on free and paid plans. See Pricing and Plans and limits.
- Manage in Settings — Open Settings → Organization to invite members and configure monitor access.
Concurrent crawl limits, paid CI entitlement, projects, and cross-environment compare apply at the organization level—not per user.
Roles
| Role | Capabilities |
|---|---|
| Owner | Full read/write on monitors, schedules, ignore rules, and projects (when paid). Invite and remove members, configure per-monitor access, and manage Stripe billing on paid plans. |
| Member | Read and write runs, schedules, and ignore rules for monitors they can access. Cannot invite members or manage billing. |
| Viewer | Read-only access to run history and reports for monitors they can access. Cannot start crawls, edit schedules, or change ignore rules. |
Owners always see every monitor in the organization. Members and viewers may be restricted to specific monitors—see Monitor access below.
Invite members
- Sign in and open Settings.
- In the Organization card, enter the colleague's GitHub username (not email).
- Choose Member (read/write) or Viewer (read-only).
- Click Add member. They see shared runs on their next dashboard visit—no separate checkout required.
Only the organization Owner can invite or remove members. The sole owner cannot remove themselves; promote another owner first (contact support if needed).
Monitor access (site grants)
By default, members and viewers can see all monitors in the organization. Owners can optionally restrict a person to specific monitors using Monitors & access on Settings.
- No grants — Member or viewer sees every site the organization has crawled.
- One or more grants — That person sees only the listed monitors (useful for agencies or large teams).
- Owners — Always see all monitors regardless of grants.
Site grants filter dashboard history and report access. They do not create separate billing or plan tiers.
Billing
Paid plans apply to the whole organization. When the Owner completes checkout on Pricing, every member benefits from CI API keys, cross-environment compare, higher concurrency, and customer agents—subject to their role and monitor access.
- Manage subscription — Only the organization Owner sees billing controls on Pricing, Settings, and Developers → API keys.
- Members and viewers — Can use paid features the org is entitled to, but cannot open the Stripe billing portal.
- Cancel or expiry — When the org's paid key expires, CI and paid-tier limits revert for everyone. See Plans and limits — subscription cancel.
Next steps
- Settings — Invite members and configure monitor access.
- Plans and limits — Feature matrix and org-level concurrency.
- API keys lifecycle — Org-scoped CI keys and rotation.
- Pricing — Compare free and paid plans for your team.