Skip to content

Commit 0098702

Browse files
Clarify 2FA and recovery code behavior for EMU setup user (#59725)
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
1 parent 0660e9c commit 0098702

1 file changed

Lines changed: 9 additions & 4 deletions

File tree

  • content/admin/concepts/identity-and-access-management

content/admin/concepts/identity-and-access-management/setup-user.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,16 +15,21 @@ The setup user is **only** intended to be used for:
1515

1616
* Configuring authentication and provisioning
1717
* SCIM provisioning via its {% data variables.product.pat_generic %}
18-
* Regaining access to your enterprise in the event of an issue with your identity provider, by utilizing the enterprise's SAML recovery codes
18+
* Regaining access to your enterprise in the event of an issue with your identity provider, by utilizing the enterprise's recovery codes
1919

2020
For other enterprise administration tasks, such as creating organizations, use a provisioned managed user account with the appropriate administrative role.
2121

2222
## How do I sign in as the setup user?
2323

24-
After we create your enterprise, you will receive an **email** inviting you to choose a password for the setup user.
24+
After we create your enterprise, you will receive an **email** inviting you to choose a password for the setup user.
2525

26-
When you create the password, you should enable two-factor authentication (2FA) for the account. All subsequent login attempts for the setup user account will require a successful 2FA challenge response.
26+
When you create the password, you should enable two-factor authentication (2FA) for the account.
2727

28-
If the enterprise account has enabled single sign-on and the setup user has **not** enabled 2FA, they must use an enterprise recovery code to authenticate. To avoid being locked out of your account, after enabling single sign-on, **save your enterprise recovery codes**. See [AUTOTITLE](/admin/managing-iam/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes#downloading-codes-for-an-enterprise-with-enterprise-managed-users).
28+
Unlike provisioned managed users, the setup user cannot sign in via SSO. Instead, the following applies:
29+
30+
* **With 2FA enabled**: All subsequent login attempts for the setup user account will require a successful 2FA challenge response. After completing the 2FA challenge, you will be prompted for a recovery code. You can skip this prompt and navigate directly to {% data variables.product.prodname_dotcom_the_website %} to access the setup user account. However, accessing your enterprise settings will always require a recovery code.
31+
* **Without 2FA enabled**: You must provide a recovery code every time you sign in.
32+
33+
We strongly recommend enabling 2FA on the setup user to avoid needing a recovery code for every sign-in attempt. To avoid being locked out of your account, after enabling single sign-on, **save your recovery codes**. See [AUTOTITLE](/admin/managing-iam/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes#downloading-codes-for-an-enterprise-with-enterprise-managed-users).
2934

3035
{% data reusables.enterprise-accounts.emu-password-reset-session %}

0 commit comments

Comments
 (0)