Pre-registered onboarding enrolls the user and device in the identity platform before the credential reaches the employee, while standard self-enrollment requires the user to register the credential themselves. The first model reduces friction, removes avoidable security decisions from users, and supports more controlled rollout. The second is simpler to initiate, but it usually leaves more room for error and phishing risk.
How pre-registered onboarding changes the enrolment path
Pre-registered onboarding shifts the first trusted step away from the employee and into the identity team or provisioning workflow. The account, device binding, and initial policy decision are established before the credential is handed over, so the user is not making a fresh security choice at sign-in time. That changes the rollout from user-led setup to controlled activation.
For passkeys, that usually means the organisation can pair enrolment with authentication policy, device readiness checks, and recovery planning before the first use. It also gives teams a clearer place to enforce lifecycle controls through the Joiner-Mover-Leaver (JML) Guide so the credential is issued as part of a managed onboarding event rather than as an ad hoc action.
Why self-enrollment feels simpler but creates more room for variation
Standard self-enrollment pushes the enrolment step to the end user, which makes it easier to start at scale and avoids some operational bottlenecks. The trade-off is that the outcome depends more heavily on user behaviour, browser or device choice, and whether the person understands what they are confirming when the passkey is created.
That is why self-enrollment can be perfectly workable in low-risk or well-instructed environments, but it is also where inconsistent setup and avoidable mistakes tend to appear. The difference is not just convenience, it is control: self-enrollment leaves more of the trust decision in the hands of the person who is least likely to distinguish a legitimate prompt from a deceptive one.
For teams comparing rollout methods, the Passwordless and Passkeys Guide is a useful reference for how passkeys support phishing-resistant sign-in and how recovery affects deployment choices.
What the difference means for rollout, recovery, and support
The practical difference shows up most clearly in rollout governance and support burden. Pre-registered onboarding usually lets the organisation standardise device eligibility, recovery posture, and communications before the credential is active, which reduces surprises later. Self-enrollment can scale faster, but it often produces more help desk variation because users encounter setup errors, missing device support, or confusion about how the passkey is stored.
That also affects recovery design. If onboarding is controlled up front, the organisation can decide in advance how to handle lost devices, employee transfers, or replacement phones. If users self-enrol without much structure, the recovery path often becomes the real weak point, because the account may be secure at first but harder to administer consistently after the initial setup.
The distinction is easy to miss when teams focus only on first login. In practice, onboarding method determines how much of the credential lifecycle is governed at issuance, not just how quickly users can complete registration.
Risk and Threat Considerations
Self-enrollment increases exposure when the user is asked to make security decisions without enough context, especially during first-use setup and recovery. A weaker onboarding process can make phishing, prompt confusion, and account recovery abuse more likely because the organisation has fewer guardrails before the credential becomes valid.
Failure mechanism: The registration flow depends on the user correctly identifying the legitimate enrolment path and completing setup on the intended device, while attackers try to exploit confusion, imitation prompts, or weak recovery handling to capture or redirect the credential.
Impact: If the wrong device, account, or recovery route is accepted, the organisation can end up with an authentic credential that is bound to the wrong trust decision, which increases the chance of account takeover or support-mediated compromise.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Passkey enrolment and phishing-resistant auth sit directly in digital identity guidance. |
| Recommendation — Apply the guidelines to choose phishing-resistant enrolment and recovery flows. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | The question turns on how authenticators are issued, bound, and recovered. |
| IA-2 — Identification and Authentication (Organizational Users) | Employee onboarding involves authenticating organisational users during initial access. | |
| Recommendation — Manage passkey issuance and lifecycle so enrolment and recovery stay controlled. Verify organisational users before activating their initial access path. | ||
| CIS Controls v8 | CIS-5 — Account Management | Onboarding method changes how accounts and access are provisioned and governed. |
| Recommendation — Standardise account provisioning so enrolment follows approved access workflows. | ||
Practitioner Guidance
What to verify: Before choosing a rollout model, verify whether the organisation can bind the user, device, and recovery policy before first use. If you cannot reliably do that, self-enrollment needs stronger guidance, tighter recovery controls, and more careful monitoring of failed or unusual enrolment attempts.
Decision rule: Use pre-registered onboarding when you need tighter control over device eligibility, recovery, or rollout sequencing. Use self-enrollment when speed matters more and the environment can tolerate a broader range of user-led setup paths.
What good looks like: A good implementation produces the same outcome every time: the right user, on the right device, with a clear recovery path and no dependence on informal instructions or last-minute support intervention.
Practitioner takeaway: The main difference is not simply who clicks the enrolment button, it is who controls the trust decision before the passkey becomes usable.
Related resources from NHI Mgmt Group
- How should organisations secure MFA self-enrollment when accounts have not yet registered a second factor?
- What breaks when self-service password reset still trusts pre-registered factors?
- When should organisations prioritise passkey provisioning over self-service enrollment?
- How should organisations verify identities in self-service onboarding?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org