Skip to content
Pathwatch Docs

Organisations & teams

Every PathWatch resource — monitors, alerts, status pages, runners, billing — is scoped to an organisation. There’s no cross-org visibility.

Personal vs team orgs

On signup, you get one personal organisation automatically. Personal orgs:

  • Can hold monitors, alerts, status pages.
  • Can pay for a Starter or Pro plan.
  • Can’t invite other members — they’re solo by design.
  • Can’t access RBAC roles (Pro+ feature).

A team organisation is created explicitly via Settings → Billing → Create team organisation. Team orgs:

  • Support invites and multiple members.
  • Get RBAC role assignments on Pro+.
  • Can be on any plan including Business.

If you started solo and now need teammates, create a team org and migrate your monitors — there’s no automatic conversion because billing, members, and entitlements are all org-scoped.

Switching orgs

The org switcher is in the header next to your avatar. Switching changes the org the rest of the app operates against — every monitor, alert, status page list updates instantly.

The currently-active org persists across sessions on the same device. New devices default to your personal org until you switch.

Inviting members

Team orgs only. Settings → Members → Invite member with:

  • Email — they don’t need a PathWatch account first; they’ll create one as part of accepting.
  • Role — see RBAC roles for what each one grants.

The invitee receives an email with a one-time link. The link is valid for 7 days; after that you’ll need to re-invite. The invite binds to the specific email — if they sign up with a different address it won’t apply.

Removing members

Settings → Members → Remove. Removal is immediate:

  • Their session for this org ends at the next request.
  • Any API keys they created stay valid until you revoke them.
  • Audit log entries they wrote remain (no rewriting history).
  • Monitors / alerts / status pages they created stay — those belong to the org, not the user.

Default org

The “default org” is what the WebUI selects on sign-in if you don’t have a session-active org. Set it at Settings → Account. Useful when you spend 90% of your time in one team org but keep a personal org for side projects.

Deleting an org

Deleting an org is destructive and irreversible. Everything scoped to the org is removed — monitors, alerts, status pages, runners, billing records, audit log. Subscriptions are cancelled through Paddle as part of the deletion flow.

The deletion is scheduled with a grace period (configurable in Settings → Account → Delete account). During the grace period the org is read-only; a re-sign-in cancels the deletion.

You can’t delete your personal org — it persists with your user record. Delete the user account if you want to leave entirely; see data export for the export-then-delete flow.