Skip to main content
This page is for the administrator taking a workspace from sample mode to real employees. When you finish, every factor, flow and use case has been checked against your real directory, your team is invited, and a pilot group can verify.

Before you start

  • A workspace you have explored in sample mode. See Quickstart.
  • Rights to connect your directory: an Entra ID administrator who can grant admin consent, or an Okta administrator who can create an API Services app. See Connect your directory.
  • A pilot group in your directory, ideally 10 to 50 people who know they are piloting.

What changes when you connect a directory

Connecting a directory is the switch from sample mode to live mode.
  • Sample employees are replaced by lookups against your directory.
  • Factors, flows and use cases you built are kept.
  • Each factor’s availability is recalculated from real attribute coverage. A factor that worked for every sample employee may only work for some real ones; for example, SMS needs a mobile number in E.164 format and Knowledge needs the attributes its questions use.
  • Use case rules that named sample groups need real groups.

The Get started checklist

The Get started card at the bottom of the console sidebar tracks setup. Before a directory is connected it shows learning tasks; after, it shows the go-live tasks. Set up recovery is added for Owners when the workspace uses enterprise SSO and no break-glass passkey is registered, so an Owner can still get in if the identity provider is down. See Sign-in, SSO and passkeys.

Review your setup

Fix your factors, Check your flows and Set who gets what open the Review your setup dialog. It checks your factors, flows and use cases against the connected directory and lists anything that would stop a verification or limit who can use it. Each item has a status: For each item you can:
  • Apply fix: for factors, set the directory attribute the review recommends.
  • Accept as-is: go live with it as it is, even for a blocker. The item shows as accepted, and Undo brings it back.
  • Open in Factors, Open in Flows or Open in Use cases: go to the setting and change it yourself.
Choose Finish later to come back to it, or Done when everything is resolved or accepted.

Roll out

1

Route the pilot group

In Use Cases, add a rule that sends your pilot group to the flow you want them to use for each use case they will hit. Leave Everyone else on a flow you are comfortable with. See How use cases work.
2

Verify yourself

From the help desk app, send yourself a verification on a phone and complete it. Confirm it appears in Activity.
3

Invite your team

Invite admins and help desk agents from Settings → Team. See Team and roles.
4

Brief people

Share What to expect with the pilot group and the Agent guide with agents.
5

Confirm the basics

Credential health is green (see Credential health), storage is the one you want (see Storage), and you know how you will export audit records (see Activity and export).
You are live when the first real request from an agent succeeds for a pilot employee.

After the pilot

Widen the use case rules to more groups as directory coverage allows, connect your own storage if you have not, and add the connectors you need: ServiceNow, Microsoft Teams, Windows TAP or PingOne MFA.