What an organisation is
Everything in the product belongs to an organisation rather than to a person: the monitored domains, the check history, the API tokens and the plan. One is created for you when you sign up - named after what you typed, or after your email address if you left it blank.
That is why your data survives a person leaving, and why an API token acts on an organisation rather than on your account.
Seats and roles
- Seat
- A place on the organisation that a person occupies. Plans sell seats: Free has one, Pro includes eight.
- Role
- What that person may do. Your own role is shown on the panel’s Organisation tab, alongside the seat you hold.
On Free there is exactly one seat and nothing to manage - that is the plan working as sold, not an error, and the panel says so in those words rather than showing an empty table.
Isolation
Your report data is visible to your organisation and to nobody else. Where a resource belongs to another organisation the API answers as though it does not exist rather than telling you it exists but is forbidden - a "forbidden" answer confirms the resource is real, which is itself a leak.
What is not built yet
You can see the organisation; you cannot yet change it
Inviting a member, changing somebody’s role, renaming the organisation and editing your own profile are not built in the panel. The Organisation tab lists what exists and says plainly where a route refused, rather than showing controls that would fail.
Some routes also refuse an interactive browser session by design, because the session is not scoped to one organisation and the API will not guess which one you meant. Where that happens the panel prints the API’s own message.