First steps
A checklist for setting up a brand-new instance: directory, login, branding, first application, and admins.
This checklist gets a brand-new instance to the point where real users can sign in to a real application. Each step links to the section that covers it in depth.
The console's own Getting started page complements this checklist. On a new instance it asks a few short questions about your focus (workforce or customer identity, your priorities, and any relevant compliance frameworks), then builds a tailored checklist and ticks each item off automatically as you complete it. Steps that do not apply can be skipped, which is reversible, and you can reopen the questions at any time with Adjust focus. Your answers apply to the whole instance. Use that page to track progress and this one for the detail.
1. Review your license
Open Settings → License & subscription and confirm your tier, add-ons (CIAM / DIAM), and limits. This determines which areas of the console are available as you proceed.
2. Set up a directory
Decide where your users live. Under User directories:
- For self-managed users, use the built-in local directory.
- To authenticate against Active Directory or LDAP, create an enterprise directory, install an Enterprise Connector, and configure sync.
While you are there, set the directory's password policy and which authentication methods (password, passkey, Kerberos) are allowed. (Session lifetime and idle timeout are instance-wide, under Settings → Login.)
3. Configure branding
Under Branding → Appearance, set your theme and accent color — this is what users see on the login page. Your logo and the enabled login languages are set under Settings → General. If you have the relevant features, configure a custom mail provider and SMS gateway so notifications and one-time codes are sent from your own infrastructure.
4. Harden authentication
- Review Multi-factor authentication under Security → MFA and enable the factors you want to offer.
- Confirm Threat protection is on under Security → Threat protection — breached-password and bot protection are enabled by default.
- If your plan includes them, define authentication policies for conditional access.
5. Add your first application
Under Integrations → Applications, add an application — either from the catalog of pre-built integrations or as a custom OIDC, SAML, or WS-Federation app. Configure its redirect URIs (OIDC) or ACS URL (SAML), then assign it to the users, groups, or directories that should have access.
6. Invite your admin team
Under Governance → Admin Console Users, add the colleagues who will help operate the platform and assign each an appropriate access level (owner, operator, auditor, …). Grant the least privilege that still lets each person do their job.
7. Verify the audit trail
Open Monitoring → Audit logs and confirm events are being recorded. This is your record of who did what, and it is tamper-evident — keep it in mind as the source of truth when investigating later.
8. Add-on steps (optional)
Depending on the add-ons your plan includes:
- Connections — to let users sign in with a social provider or a partner's corporate IdP, add a Connection. The platform stays the single front door your applications trust.
- Device trust (DIAM) — to bring endpoints under management, configure enrollment under Device settings, roll out the device client, and confirm devices appear in the Device inventory.
- Organizations (CIAM-B2B) — to onboard a business customer and let their own admin manage members, create an organization and grant a delegated admin.
You're set up
From here, day-to-day work is mostly in Directories (managing people) and Integrations (connecting applications). Use the Admin Console tour as a map, and the glossary whenever a term is unfamiliar.