Skip to content

Commit 32b13b5

Browse files
authored
Add "instructions" for deleting the setup user (#59629)
1 parent 41f6c67 commit 32b13b5

1 file changed

Lines changed: 23 additions & 11 deletions

File tree

  • content/admin/concepts/identity-and-access-management
Lines changed: 23 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Setup user
3-
intro: 'The setup user is used to configure authentication and provisioning for {% data variables.product.prodname_emus %}.'
3+
intro: 'The setup user is used only to configure authentication and provisioning for {% data variables.product.prodname_emus %}.'
44
versions:
55
ghec: '*'
66
topics:
@@ -11,25 +11,37 @@ topics:
1111

1212
## How should I use the setup user?
1313

14-
The setup user is **only** intended to be used for:
14+
The setup user is an administrative account. It 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 recovery codes
18+
* Regaining access to your enterprise in the event of an issue with your identity provider
1919

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

22-
## How do I sign in as the setup user?
22+
## What is the setup user's username?
23+
24+
If you use **{% data variables.product.prodname_dotcom_the_website %}**, the username is your enterprise's shortcode, suffixed with `_admin`. For example: `fabrikam_admin`.
2325

24-
After we create your enterprise, you will receive an **email** inviting you to choose a password for the setup user.
26+
If you use **{% data variables.enterprise.data_residency_site %}**, the username is a randomly generated shortcode, suffixed with `_admin`.
27+
28+
## How do I sign in as the setup user?
2529

26-
When you create the password, you should enable two-factor authentication (2FA) for the account.
30+
After we create your enterprise, you will receive an **email** inviting you to choose a password for the setup user.
2731

28-
Unlike provisioned managed users, the setup user cannot sign in via SSO. Instead, the following applies:
32+
When you create the password, we strongly recommend that you **enable two-factor authentication (2FA)** for the account and **save your recovery codes**.
2933

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.
34+
Unlike provisioned managed users, the setup user cannot sign in via SSO.
3235

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).
36+
- **Without 2FA enabled**, you must provide a recovery code **every** time you sign in.
37+
- If **2FA is enabled**, you can sign in with a successful 2FA challenge response. You only need to provide a recovery code to access enterprise settings.
3438

3539
{% data reusables.enterprise-accounts.emu-password-reset-session %}
40+
41+
## Can I delete the setup user?
42+
43+
The setup user **cannot** be deleted, because it is essential for maintaining authentication and provisioning. The only way to remove the setup user is to delete your enterprise account. See [AUTOTITLE](/admin/managing-your-enterprise-account/deleting-an-enterprise-account).
44+
45+
## Further reading
46+
47+
- [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)

0 commit comments

Comments
 (0)