Check that a second admin can reset passwords and add or delete users ( Google), limit their roles, and protect admin logins with 2-step sign-in.
Backup admin checklist: the short answer
If you're a super administrator for a domain-verified Google Workspace account, you can make someone else in your organization an administrator to help you perform management tasks. This way, if you're busy or on vacation, someone else can help with tasks like resetting passwords and adding or deleting user accounts. List every tool your sellers log into and write down the one other person who could reset a seller's password if you were out tomorrow.
Key takeaways
- Name and limit the second admin. Google notes that exactly what an administrator can manage depends on the roles or privileges you assign. Share management of your organization's account only with people you trust. This limits the scope of their power while ensuring someone else can handle user resets.
- Protect admin accounts with verification. Google recommends that all team admins protect their accounts with 2-Step Verification. This adds a required step during sign-in that helps secure the accounts holding administrative rights.
- Create emergency accounts. They provide a "break glass" option if normal administrative access fails.
- Store recovery codes. Keep them stored securely so that losing credentials does not lock you out permanently.
Before the new seller starts: name and limit the second admin
Name a specific person who can manage user accounts when you are away. In Google Workspace, an administrator account is defined as a workspace account that has access to the Google Admin console Google. Choose this person with care, and do not grant broad permissions to anyone outside your trusted circle.
Limit what this second admin can actually do. Assign only the specific roles needed for resetting passwords or adding new sellers. Avoid giving full administrative control if a narrower role covers the task. This approach keeps the scope of their power tight and aligned with your team's needs.
Check that the chosen person understands their limits. They need to know which actions fall under their assigned roles. If they lack a specific privilege, they cannot perform that action in the console. Review the role definitions before the new seller starts work. Ensure the backup admin knows how to access the console using their own credentials.
Keep the list of admins short. Adding more people increases the surface area for error. Stick to one primary backup unless your team size demands otherwise. Document the exact roles you assigned in your internal notes. This record helps you verify permissions later without guessing what was granted.
Illustrative example: a 5-tool team
A sales manager runs 5 tools for a team of 10 sellers. The manager lists all 5 tools in one sheet, names 1 backup admin for each tool, and writes each admin's role beside their name. The backup admin signs in with their own account and tests a password reset on a practice user. The manager sets a reminder to recheck the sheet every 90 days. This schedule is the manager's own choice for this example, not a vendor rule.
During setup: sign-in protection and emergency accounts
Protect the administrator accounts before handing over any access. Two-step sign-in adds a second layer of confirmation when signing in, which is critical for the person who can reset other users' passwords. If you use Microsoft Entra ID for your identity management, you should create two or more emergency access accounts in your organization to reduce the impact of accidental lack of administrative access. These accounts act as a safety net if your primary admin credentials are locked or unavailable.
When setting up these emergency accounts, use different authentication methods than your normal daily logins. For example, if your normal administrator account uses the Microsoft Authenticator app for strong authentication, use a FIDO2 security key for your emergency accounts according to Microsoft. This separation ensures that a failure in one authentication method does not lock out both your standard and emergency access paths. You must treat these emergency accounts strictly as break-glass tools. Use them only for emergency or "break glass" scenarios where normal administrative accounts cannot be used. Do not grant these accounts to new hires or keep them active for routine tasks.
Restrict emergency account use to only the times when it's absolutely necessary. This limitation keeps the audit trail clean and prevents accidental changes made during non-critical periods. If you are onboarding a new rep, ensure they do not have access to these specific break-glass credentials. Their access should remain within the standard user or limited admin roles discussed in the previous section. By keeping emergency access isolated and protected by distinct hardware keys, you maintain a reliable recovery path without compromising the security of your day-to-day operations. Write down the location of the physical security keys and share this information only with the designated backup admin.
Backup admin reference table
The rules below come directly from each publisher's documentation. Each row states what that specific source documents about admin roles, emergency access, or recovery limits.
| Publisher | Documented Admin/Recovery Rule |
|---|---|
| A super administrator for a domain-verified account can make someone else an administrator to help perform management tasks. | |
| Microsoft | You can reduce the impact of accidental lack of administrative access by creating two or more emergency access accounts. |
| HubSpot | Super Admin permissions are required to view and export audit logs. |
| GitHub Docs | Support will not restore access to accounts with two-factor authentication enabled if you lose your credentials or recovery methods. |
| Amazon | Use the root user only to perform the tasks that require root-level permissions. |
These entries reflect distinct vendor policies rather than a single universal standard. For example, while Microsoft advises multiple emergency accounts, GitHub Docs notes that support cannot bypass lost two-factor credentials. Your backup plan must account for these separate limitations across your stack.
After go-live: 90-day tests and audit log reads
Once the new seller is active, your job shifts from setup to verification. Confirm that the emergency access paths you created actually work when needed. Microsoft advises validating account functionality at least every ninety days. This interval applies specifically to emergency access admin accounts within Microsoft Entra ID. Do not treat this as a universal legal deadline; it is a recommended validation frequency for this specific product's security posture. If you manage multiple vendors, check each one’s documentation separately, as rules vary by platform.
The validation process involves more than just checking if a password works. According to Microsoft, regular validation drills should include reviewing the authorized-user list. You also need to test sign-in and administrative task functionality during these drills. This ensures the person holding the emergency credentials can actually perform the tasks required to recover a locked-out user. Write down the date of each drill in your internal notes so you have a record of when the last successful test occurred.
While testing emergency access, verify who has permission to see what happened during those tests. In HubSpot, Super Admin permissions are required to view and export audit logs. If your backup admin does not hold this specific role, they cannot review the activity history generated by their own emergency actions. The centralized audit log allows you to view user actions in your account. This visibility is critical for confirming that the emergency account was used correctly and did not trigger unintended changes. For the coaching side of your records, see sales coaching logs.
Keep your records separate from the vendor's interface. In HubSpot, exporting logs requires the Super Admin permissions mentioned above. Store these exports in a secure location accessible only to you and your designated backup admin. This creates a local record that persists even if the vendor's retention policies change or if the online view becomes inaccessible. Use these exported files to cross-reference with your internal validation drill notes.
Final checks and the checklist
The final two checks focus on preventing permanent lockouts by managing high-privilege accounts correctly. Amazon advises using the root user only to perform tasks that require root-level permissions Amazon. This limitation ensures that routine administrative work does not rely on the most powerful credential in the system. Similarly, GitHub Docs states that for security reasons, support will not be able to restore access to accounts with two-factor authentication enabled if you lose your credentials or recovery methods GitHub Docs. Because this recovery path is closed when those items are lost, storing recovery codes becomes a critical preventative measure rather than an optional backup. HubSpot notes that subscription type logs are available from April 15, 2025 HubSpot. Knowing this start date helps managers understand which historical data points are accessible for auditing purposes during their review cycles.
These specific rules highlight why generic admin advice often fails for sales teams using multiple platforms. Each vendor defines its own boundaries for emergency access. The following table summarizes the eight core actions required to maintain secure, recoverable login management across your stack.
| Check # | Action item |
|---|---|
| 1 | Name a second admin |
| 2 | Limit admin roles |
| 3 | Turn on 2-step sign-in |
| 4 | Set up emergency accounts |
| 5 | Test Entra emergency accounts every 90 days |
| 6 | Check who can read logs |
| 7 | Keep recovery codes |
| 8 | Keep root use rare |
Use this checklist before the new rep starts. If a tool has no named backup administrator, assign one immediately. Going through these eight lines helps you spot the tools that still lack one. When a seller leaves, also review seller login removal.
FAQ: backup admin for sales tools
What is a backup admin checklist for sales tools?
It is a list of eight checks covering naming a second admin, limiting roles, enabling 2-step sign-in, setting up emergency accounts, testing Entra emergency accounts every 90 days, checking log readers, keeping recovery codes, and keeping root use rare. This structure gives you a clear path for password resets and user management when you are unavailable. The checks address specific vendor documentation regarding administrative permissions and security protocols. You should review each item to confirm your team's current setup matches these documented standards.
How often should backup admin access be tested?
For Microsoft Entra emergency accounts, Microsoft recommends validating account functionality at least every 90 days. This validation includes reviewing the authorized-user list and testing sign-in functionality for emergency access accounts. It is not a legal deadline but a suggested frequency for operational readiness.
Who can view and export audit logs in HubSpot?
HubSpot requires Super Admin permissions to view and export audit logs. These logs include security activity within the last 30 days. Only users with this specific permission level can access this historical data. Ensure your designated backup administrator holds this role if they need to review recent security events.
Can GitHub Support restore a locked account that uses two-factor authentication?
No, GitHub Docs states that support will not restore access to accounts with two-factor authentication enabled if you lose your credentials or recovery methods. For security reasons, this restriction applies strictly to 2FA-enabled accounts. You must store recovery codes securely to avoid permanent lockout. This limitation makes proactive storage of recovery methods essential.
Does the two emergency accounts advice apply to the tools my team uses?
The advice to create two or more emergency access accounts is specifically Microsoft guidance for its own admin accounts. It aims to reduce the impact of accidental lack of administrative access. Other vendors may have different requirements or structures for emergency access. Check each tool’s specific documentation to determine their unique recommendations for backup administrators.