You are a tenant administrator. That means one of your organisation's tenants — a per-environment slice of IntelliAuth like production-cymmetri, staging-cymmetri, or uat-cymmetri — is yours to run.
This part of the docs is for you. It covers the day-to-day:
Register the applications your team is building.
Manage users — invite, edit, disable, force MFA reset.
Configure the authentication policy — what factors, what flows, what risk thresholds.
Compose Flows and Actions for any custom logic at sign-in.
Brand the sign-in experience so users see your colours and logo.
Read the audit log, set up reports, and stream events to your SIEM.
Decide who else from your team has access to this tenant admin console.
Everything you do here is via the web console at https://<tenant>-<org>.<your-domain>/admin. There is no REST API for tenant admin operations. This is deliberate — every action on this surface is human-authored, audit-logged, and reversible by a known human actor.
If you are also a developer integrating IntelliAuth into your product, you want the developer docs as well. The two audiences are deliberately distinct: tenant admins configure; developers integrate. They use different surfaces and reach for different docs.
What's NOT here
Things that look related but live elsewhere:
Organisation-level controls (creating new tenants, billing, plan changes, platform-level audit) — those live in the IntelliAuth admin console at
https://manage.<your-domain>, operated by your organisation's platform administrator. See the control plane admin docs.Integrating IntelliAuth into your app — that's the developer audience.
End-user account self-service (signed-in users editing their own profile, sessions, MFA factors) — your users do that in their own profile area, not the admin console.
Where to start
If you're new to the console: console tour.
If you just received an invitation to a fresh tenant: first-time setup.
If you want the conceptual map before clicking around: core concepts.