Define identity boundaries
Decide which users are customers, employees, administrators, service identities or test users, and whether separate profile attributes or lifecycle rules apply.
Review user management ↗Administrator setup
A practical checklist for configuring identity safely.
Use this as a setup and review sequence. It links into the console documentation rather than reproducing every setting, and it deliberately separates decisions your organisation must make from product configuration.
Before you begin: confirm the relevant features are enabled in your environment and agree on a test tenant. The items below are a review checklist, not a substitute for environment-specific security review.
Set up tenant structure
Define tenant ownership, membership, groups, domains and the boundaries available to tenant administrators.
Review accounts and tenants ↗Connect an application
Choose SAML or OAuth2/OIDC based on the application type and document the protocol-specific integration settings.
Configure applications ↗Set up provisioning and mappings
Where required, plan SCIM and the profile/domain mapping rules used to classify or provision identities. Validate mappings with a controlled test.
Configure automation ↗Define authorization
Assign the appropriate roles and group membership, and review scope/resource access for the intended tasks.
Review authorization ↗Set assurance and network rules
Document authenticator assurance requirements, session expectations, network allow/deny lists and rate-limit policies for sensitive users and integrations.
Review security settings ↗Prepare support procedures
Define what support agents may do, which actions require extra verification and where escalation is needed. Do not treat support access as an alternate authentication path.
Review help-desk procedures ↗Verify audit and recovery behavior
Run a recovery/tabletop scenario and confirm what user, session, device and resource context is visible to the people who investigate incidents.
Review logs and troubleshooting ↗Configuration details
Open the console documentation
Detailed console paths and troubleshooting notes are maintained in the console reference.
Open help docs →Integration details
Inspect documented endpoints
Use the API reference to confirm operation details before building or changing provisioning flows.
Open API reference →