Back to Home

Organization management

An Organization is the top-level tenant in Unit Oncall. Teams, Schedules, Webhooks, alerts, billing, and audit logs all live inside an Organization, and a user can belong to more than one. This page covers creating, switching, and deleting Organizations. For the long list of per-Organization settings, see Organization settings.

Creating an Organization

From the console, open New Organization and provide:

  • Name — the display name of the Organization.
  • Slug — a URL-safe identifier used in links. Must be unique.
  • Description — optional, free text.

The user who creates the Organization is automatically added as its owner (see Roles and permissions). From there you can invite the rest of your Team — see Member invitation.

Switching between Organizations

If you belong to more than one Organization, use the Organization switcher in the top navigation. Switching:

  • Re-issues your session for the new Organization, so audit and routing decisions are scoped correctly.
  • May ask you to satisfy any MFA or required SSO policy the destination Organization enforces, even if you already signed in.

Signing in and entering an Organization are separate steps — see Authentication.

Updating Organization settings

Owners and admins can change the Organization's profile (name, description, locale, timezone) and its governance options (membership rules, MFA requirement, allowed email domains, required SSO providers, AI feature toggles). All of these are documented field-by-field in Organization settings.

Deleting an Organization

Organization deletion is a deliberate, multi-step flow with a built-in grace period so it can be reversed if requested by mistake:

  1. Owner-only action. Only the Organization owner can start the flow (see Roles and permissions).
  2. Pre-checks. Before deletion can be scheduled, the Organization must have no active subscription. Cancel or expire the subscription first if needed.
  3. Request deletion. The console schedules the deletion at a future time (scheduled_delete_at) and immediately disables incoming webhooks so the Organization stops accepting new alerts.
  4. Cancel any time before the scheduled time. Cancelling restores the Organization (webhooks re-enabled, deletion call-off recorded in the audit log).
  5. Automatic deletion. If not cancelled, a background job permanently removes the Organization and all of its data after the scheduled time.

Both the deletion request and any cancellation are recorded in Audit logs.

Related