Skip to content

Welcome, control plane admins

The IntelliAuth control plane is the platform layer that creates, manages, and observes tenants. If you're operating IntelliAuth for an organisation — provisioning tenants for customers, setting platform-wide policy, watching the provisioning workflow that stands a new tenant up end to end — this is your surface.

The control plane sits one layer above tenants. Each tenant is its own isolated authentication environment with its own data, configuration, and traffic boundary. The control plane is what stands tenants up, tears them down, and reports on them.

  • Provision a tenant end-to-end. The control plane allocates the tenant's resources, deploys its workloads, and waits for everything to come up healthy. The whole sequence is one click in the console; it takes anywhere from 30 seconds to a few minutes.
  • Manage the tenant lifecycle. Suspend a tenant to pause its auth traffic. Resume to put it back. Decommission to release resources without losing the audit history. Tenant lifecycle walks through the states and valid transitions.
  • Set platform policy. Plans, rate limits, MFA defaults for new tenants — anything that should be true across every tenant the org operates.
  • Observe. Tenant-level health, saga progress, the org-scoped audit feed.

Tenant admins (the next audience over in the docs) handle the day-to-day of their own tenant: users, applications, MFA, branding, audit log retention. The control plane creates the tenant; the tenant admin runs it.

If you're operating IntelliAuth for the first time:

  1. Read Tenant lifecycle — the six-state machine that governs every tenant the platform manages.
  2. Walk through Provision a new tenant end-to-end. Provisioning is the busiest thing happening on the platform; understanding the steps helps when something gets stuck.
  3. Skim the audit event reference so you know what shows up in the org feed when operators take actions.

This is the platform surface. Tenant admins read a different sidebar.