Organizations
The top-level account container. Everything in fastmon belongs to one.
An organization is the top-level container in fastmon. Every site, member, invite, API token, and notification rule belongs to exactly one organization; nothing crosses that line.
Why it matters
Organizations are how fastmon keeps customers apart, how billing and plans hang together, and how access control is scoped.
Most accounts only ever have one organization. Multiple is mostly a thing for agencies and partners; see the partner plan below.
When you'd touch it
- First-time setup. The "create your account" flow makes one for you.
- Adding teammates. Invite by email, give them a role.
- Buying a plan. Plans live on the organization, not the user.
- DPA or invoice request. The organization is the legal counterparty.
- Compliance review. "Who can see this data?" is answered at the organization level.
What's on an organization
| Field | Type | Notes |
|---|---|---|
id | UUID v7 | Stable identifier. Used in API URLs (/v1/organizations/{id}/…). |
name | string | Human-readable. Shows in the org switcher. |
plan | enum | beta, starter, pro, partner, or enterprise. |
members | list of { user_id, role } | Roles: owner, member. |
Plans
| Plan | When you'd be on it |
|---|---|
beta | Early access during onboarding. Limited quota. |
starter | Single-product teams. Default retention. |
pro | Production teams. Higher retention. |
partner | Agencies. Manage partner clients (sub-organizations you operate on behalf of someone else). |
enterprise | Custom limits, custom retention, signed DPA. |
The plan gates features and quotas. Which Web Vitals get collected isn't tied to the plan; every plan collects the same metrics.
Roles
| Role | Can do |
|---|---|
owner | Everything. Manage sites, members, billing, integrations. Transfer ownership. Delete the organization. |
member | View dashboards, run analytics queries, manage their own notification rules. |
There's exactly one owner at a time. Use Transfer ownership to hand it off; the previous owner becomes a member.
Common scenarios
One product, one org
The default. One organization, one billing relationship, several sites under it (acme-marketing, acme-app, acme-docs).
Multiple unrelated products
Run two unrelated brands and want billing and access cleanly separated? Create two organizations. You can be a member of both.
Agency running client sites
Use the partner plan. Each client is a partner client: a sub-organization the agency runs. Agency users see all clients; the client sees only itself.
Common surprises
- The org switcher is just UI. API requests scope by the URL (
/v1/organizations/{id}/…), not by whichever tab you've got open. - Members are global fastmon users. Invite an existing user and the existing account gets reused; no duplicate.
- Sites can't move between organizations. If you genuinely need this, ping support. No self-serve action for it.
Related
- Sites: the resources owned by an organization.
- API: Organizations endpoints: programmatic access.