Organizations

Overview

All monitoring resources — projects, services, integrations, alert rules, expectations, and incidents — are organized within an organization. Every organization is a shared workspace where all members work against the same shared inventory according to their role. The same UptimeHunt account can belong to multiple organizations at once.

UptimeHunt supports two organization types:

Every account starts with a personal organization (created automatically on sign-up), which you own and work in alone. You can create team organizations later to add members and share resources. This section documents team organization setup and administration — if you're using UptimeHunt solo, nothing here applies yet.

Key Concepts

Membership and roles

Each user in an organization holds exactly one role — Owner, Admin, or Member. Roles map to fine-grained capabilities (for example service.edit or audit.view) that gate every action in the UI and the API. See Roles & Permissions for the full matrix.

Active organization context

You can belong to several organizations. The web app shows an organization switcher; API clients select the active organization with the X-Org-Slug request header (or an organization-bound API token). Requests without any organization context fall back to your personal workspace — so existing single-user API usage keeps working unchanged — or, for organization-only accounts (team founders, invitation sign-ups, SSO-provisioned members), to their sole organization. See API Authentication — Organization Context.

Single sign-on

Team organizations can connect their own identity provider (OIDC, SAML 2.0, or Google Workspace) and optionally enforce SSO for all members. See Single Sign-On, including how UptimeHunt keeps identities from different organizations strictly separate.

Governance

Organizations get a SOC2-grade audit log of authentication, membership, configuration, and resource events, plus token oversight so Owners can review and revoke members' organization API tokens.

Creating a Team Organization

There are four ways to end up in a team organization:

1. Sign up as a team — choose Team on the sign-up page and name your organization. The organization is created together with your account, and the founder is an organization-only account: it belongs to the team organization and has no separate personal workspace.
2. Create one in the app — after sign-up, use the organization switcher's New organization action (or POST /api/v1/orgs) and name your organization. You keep your personal workspace alongside it.
3. Convert an existing personal workspace into a team organization — see the Administration guide.
4. Accept an invitation from an existing organization — see Members & Invitations.

Trial Period

Team organizations start with a 14-day trial that includes full features at no cost:

• All monitoring, alerting, and integration features are fully available.
• You can invite members and configure SSO.
• The trial has no feature limitations or artificial restrictions.

When the trial ends, read Trial semantics to understand what changes.

In This Section

• Members & Invitations — inviting users, accepting invitations, changing roles, offboarding
• Roles & Permissions — the role × capability matrix and role-granting rules
• Administration — organization settings, conversion, deletion, trials
• Single Sign-On — OIDC, SAML 2.0, Google Workspace, and GitHub; enforced SSO; identity realms
• Email Routing & Auto-Join — optional domain verification for login routing
• Audit Log — event catalog, retention, CSV export
• Token Oversight — reviewing and revoking members' organization API tokens
• Service Account Tokens — org-pinned credentials for Terraform, Ansible, and the Kubernetes operator