Organization Administration

Overview

This guide covers organization-level administration: profile settings, plans and trials, 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.

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 and Trial

Team organizations require a Team or Enterprise plan. Plan limits (such as the maximum number of members — 15 on Team, unlimited on Enterprise — and service quotas) are enforced per organization.

A team organization's billing state is one of:

The 14-day trial

Every new team organization starts with a 14-day trial that includes full features — monitoring, alerting, invitations, SSO, and everything else — with no limitations. During the trial, your organization works exactly as it would under a paid plan.

No card required — the trial is free, and no payment method is needed to start.

Expiration: automatic member blocking when over-cap

When the 14-day trial ends without a paid plan assigned, the organization enters trial_expired state. The system first checks how many members your organization has:

• Within the Team-plan member limit (15 members or fewer): the organization becomes read-only-everything, run-nothing (see below).
• Over the Team-plan member limit (16+ members): the newest-joined members are automatically blocked (in LIFO order — last one in, first one blocked) until the count equals 15. Blocked members receive no notification and see access denied errors; unblock them at any time by upgrading or removing other members first.

Blocked members are logged as member.blocked (with system=true) in the audit log, and organization Owners are notified that members have been blocked due to trial expiry.

When a trial expires: monitoring and write access

A trial_expired organization becomes read-only-everything, run-nothing:

1. Monitoring stops. Probes no longer execute any of the organization's checks, regardless of each service's enabled flag. No new check results, incidents, or alerts are produced.
2. Everything stays browsable. All read access remains — dashboards, service details, historical graphs, incidents, the audit log. A persistent "trial ended" banner is shown and services render as disabled.
3. Writes are blocked. Creating, editing, enabling, or deleting resources returns a structured 403 with code: "TRIAL_EXPIRED" (see structured errors). This applies to API clients and IaC tooling too.
4. History retention is shortened. Check results and incident history of trial-expired organizations are purged after 30 days (instead of plan-standard retention). Organization configuration — services, integrations, alert rules, blocked members — is retained longer, so assigning a plan reactivates the organization with its setup intact.

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.
• Team plan requirements apply after conversion: without a paid plan, the trial rules take effect.
• 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"}'

Related Documentation

• Roles & Permissions
• Members & Invitations
• Single Sign-On
• Email Routing & Auto-Join
• Audit Log