Organization Administration
Organization settings, plan management, workspace conversion, and organization deletion.
Organization Administration
Overview
This guide covers organization-level administration: profile settings, plans, converting a personal workspace to a team organization, and deleting an organization.
All operations here require Owner-level capabilities (org.edit, org.delete, org.convert, org.billing, sso.edit) — see Roles & Permissions.
Organization Settings
Requires org.edit.
UI: Organization → Workspace settings.
| Setting | Description |
|---|---|
| Name | Display name, shown across the UI and in invitation emails |
| Slug | URL-safe identifier used in API paths and the X-Org-Slug header. Permanent — it is referenced by API clients, IaC configurations, and SSO endpoints, so it cannot be changed |
| Logo URL | HTTPS URL of your logo image (the image itself is hosted by you) |
| Website URL | Your organization's website (optional) |
| Contact email | Administrative contact for the organization (optional) |
| Enforced SSO | Require all members to sign in through the organization IdP — see Single Sign-On |
API:
curl -X PATCH https://app.uptimehunt.io/api/v1/orgs/acme \
-H "Authorization: Bearer {access_token}" \
-H "Content-Type: application/json" \
-d '{"name": "Acme Corporation", "logo_url": "https://acme.example.com/logo.png"}'Settings changes are recorded in the audit log as org.updated with per-field old/new values.
Plans
Every organization — personal workspace or team — always has an assigned plan. A newly created organization is assigned whichever plan is flagged as the platform default (ordinarily Free); there is no trial period and no plan-less interim state.
Plan limits — the maximum number of services, cron monitors, members, private probers, status pages, monitoring regions per check, data retention, and more — are enforced per organization according to its assigned plan, plus any per-organization override. Governance-only features (SSO, the audit log, and the member-email-domain policy) are gated by plan the same way, regardless of organization type.
API:
curl https://app.uptimehunt.io/api/v1/orgs/acme \
-H "Authorization: Bearer {access_token}"The response's plan field carries the assigned plan slug (e.g. free, team, enterprise); effective_limits (also aliased as limits) carries the resolved quota values it was computed against.
Changing plans
Plan assignment is currently managed administratively — contact support to move an organization to a different plan. Once self-serve subscription billing ships, upgrading or downgrading will be available directly from Workspace settings.
Member seat limits
An organization's member capacity is a plan limit (max_org_members) like any other quota — it is not tied to organization type, and there is no fixed number across the platform: it depends on the assigned plan and any per-organization override.
Inviting a member, accepting an invitation, or unblocking a blocked member that would put the organization over its effective max_org_members (counting only active, non-blocked members) is refused with a structured 403 (code: "MEMBER_CAP_REACHED", see structured errors) — nothing is created or changed. To add more members, either free up a seat (remove or block an existing member) or move to a plan with a higher seat limit.
Email Routing Domains
Verifying ownership of an email domain (DNS TXT record) lets the login page advertise your IdP automatically to anyone entering an email under that domain. It is an optional convenience — never a prerequisite for SSO setup, JIT provisioning, or enforcement. See Email Routing & Auto-Join for the full guide.
Converting a Personal Workspace to a Team Organization
Requires org.convert (you, as the owner of your personal workspace).
If you started with a personal account and now want to collaborate, convert your workspace into a team organization — no data moves: all your projects, services, integrations, alert rules, and history stay exactly where they are, and the workspace becomes invitable.
UI: Organization → Workspace settings → Danger zone → Convert to team organization — enter the new team name to confirm.
API:
curl -X POST https://app.uptimehunt.io/api/v1/orgs/{your-slug}/convert \
-H "Authorization: Bearer {access_token}" \
-H "Content-Type: application/json" \
-d '{"name": "Acme Corporation"}'Notes:
- The organization slug is preserved (it is referenced in API client and IaC configurations); only the display name is set fresh.
- The converted organization is your organization — a new, separate personal workspace is not created.
- The organization keeps its existing assigned plan after conversion — conversion does not change or reset billing.
- The conversion is audited as
org.converted.
Deleting an Organization
Requires org.delete (Owner only). Irreversible.
Deleting a team organization permanently removes its projects, services, monitoring history, integrations, alert rules, memberships, invitations, and SSO configuration.
UI: Organization → Workspace settings → Danger zone → Delete organization — type the organization name to confirm.
API: the request body must repeat the organization name in confirm — the same deliberate type-the-name confirmation:
curl -X DELETE https://app.uptimehunt.io/api/v1/orgs/acme \
-H "Authorization: Bearer {access_token}" \
-H "Content-Type: application/json" \
-d '{"confirm": "Acme Corporation"}'Personal workspaces cannot be deleted
Only team organizations can be deleted. A personal workspace is removed only by deleting the user account itself.
Related Documentation
Roles & Permissions
Role definitions, capability matrix, grant ceiling rules, and the last-owner invariant.
Single Sign-On (SSO)
Team organizations can connect their own identity provider (IdP) so members sign in with corporate credentials. UptimeHunt supports OIDC, SAML 2.0, Google Workspace, and GitHub.