How do I regain admin access to Google Postmaster Tools if the previous manager left?
Updated on 9 Oct 2026: We clarified TXT and CNAME ownership recovery and added checks for verification errors and missing dashboard data.
Regain admin access by verifying the sending domain again from a Google account you control. If you only have dashboard access and cannot add people, you have delegated read access, not verified ownership. Add the domain in Google Postmaster Tools, publish the account-specific TXT or CNAME verification record Google supplies, and verify the domain.
Do not depend on transferring the previous manager's role inside Postmaster Tools. Google does not provide a reliable ownership handoff for this situation. Prove domain control again, create a second verified owner with a separate DNS record, and document which token belongs to each account. Re-verification adds an owner, but it does not automatically remove the former owner.
The short answer
If DNS access is available, add the sending domain to Google Postmaster Tools from your company-controlled Google account, publish the verification token Google gives you, click Verify, and then manage dashboard users from the verified account.
The fastest way to regain admin access
Start with DNS, not the former employee's login. Domain verification establishes ownership in Postmaster Tools. If your team controls the authoritative DNS zone for the sending domain, a current Google account can verify ownership even when the previous manager left without granting access.
- Choose the account: Use a current company-controlled Google or Google Workspace account. Plan for two verified owner accounts so access survives another departure.
- Add the sending domain: Enter the domain used to authenticate outgoing mail, either the DKIM d= domain or the SPF Return-Path domain, then click Create. For sending subdomains, Google recommends adding and verifying the primary domain first. Subdomains added under that verified primary domain do not need separate verification for the same account. If you need a step-by-step DNS walk-through, use this verify the domain guide.
- Publish the record: On Manage Domains, open More options and choose Verify domain. Copy the TXT or CNAME record from the Verify ownership of domain window and publish the exact hostname and value at your authoritative DNS provider. Do not reuse a token from another account.
- Verify ownership: Once the new record is visible in public DNS, return to Postmaster Tools and click Verify. Verification is usually immediate, but Google says the status can take up to 10 minutes to update. DNS propagation is separate from that status update and can take longer.
- Grant dashboard access: On Manage Domains, open the domain menu and choose Manage users, then New user. Enter each colleague's Google or Google Workspace account address and click Add. Notify them because Google does not send an access notification. For a broader handover workflow, see how to transfer ownership safely.
Google Postmaster Tools ownership recovery: verify DNS, add team access, then review the old token.
Example Google verification recordsDNS
example.com. TXT "google-site-verification=abc123exampletoken" abc123.example.com. CNAME gv-example.dv.googlehosted.com.
The exact hostname and value must come from the Google account that will own the domain. An old TXT value belongs to the old account and cannot verify the new account. If the account that lost access was also the only Google Workspace administrator, use Google admin recovery for Workspace administration. Ask another super administrator to help, or follow Google's automated recovery and any support-assisted option it offers. Restore Postmaster Tools ownership separately using DNS and another Google account.
TXT or CNAME for Postmaster Tools verification
Google's Postmaster Tools setup instructions describe both TXT and CNAME verification. Publish the exact host and value Google gives you, then keep every active owner's account-specific token documented.
TXT verification
- Best fit: Use the TXT record Google supplies and place it exactly where your DNS provider expects it.
- Tradeoff: Add the verification token as a separate TXT record. Do not overwrite or append it to your SPF record.
- Keep it: Keep every active owner's verification token published and documented. Review obsolete tokens only after replacement owners are verified.
CNAME verification
- Best fit: Use the CNAME record Google supplies and publish its exact hostname and target.
- Tradeoff: Some DNS interfaces auto-append the domain, which can create an incorrect hostname if you enter the full name.
- Cleaner DNS: A unique hostname can keep verification away from a crowded root TXT set and make later review easier.
Do not delete first
Deleting the former manager's verification record does not establish ownership for your account. Add and verify the new account-specific token first, confirm the new owner can manage users, and only then review old DNS records under your security policy.
Troubleshoot verification and missing dashboard data
A verification error, an access error and an empty dashboard need different checks. Use the symptom below to decide whether to check the account, DNS or Gmail reporting.
|
|
|
|---|---|---|
Domain will not verify | Authoritative DNS, hostname and token | Check the exact record publicly. Watch for a duplicated domain suffix in the DNS host field. Allow DNS caches to expire, then retry Verify. |
"Not authorized" or no Manage users | Signed-in account and ownership | Confirm the Google account address. If the current account has only read access and cannot start verification, verify ownership with another company-controlled account. |
Cannot add a colleague | Google account email address | Use the address associated with their Google or Google Workspace account. An ordinary email address without a Google account is insufficient. |
Verified, but no dashboard data | Authentication domain and Gmail traffic | Match the selected domain to your DKIM d= or SPF Return-Path domain. Low-volume days have privacy limits; a verified status does not guarantee dashboard data. |
Checks for common Google Postmaster Tools access recovery problems.
Google's dashboard guidance says data typically updates within 24 hours, with longer delays possible. Compliance status changes can take up to seven days. These dashboards cover personal Gmail traffic, and Compliance status aggregates subdomains under the primary domain.
What happens to the former owner's access
Verifying the same sending domain from a new Google account creates another verified owner. It does not transfer ownership away from the former manager. Google's current help explains how owners add dashboard users, but it does not document a dependable control for one verified owner to remove another verified owner.
- Company-managed account: Suspend or secure the former manager's Google Workspace account through your normal identity and offboarding controls.
- Personal or external account: Do not attempt account recovery. Verify current owners through company-controlled DNS and record the residual access risk.
- Old DNS token: Identify which account and Google services use the record before removing it, and confirm replacement owners work first. Do not treat deletion as a documented immediate revocation method.
- Delegated user: Review Manage users and remove read access where the interface permits it. Delegated access is separate from verified ownership.
Ownership and Workspace administration are separate
A Google Workspace administrator is not automatically a Postmaster Tools owner. Verify the domain for the new Google account to establish ownership. An existing verified owner can grant dashboard read access, which does not make the recipient an owner.
Secure old access without breaking visibility
After the new account verifies successfully, handle the former manager's account through your offboarding process. The goal is to secure company-controlled access, document any owner that cannot be removed in Postmaster Tools, and avoid another recovery later.
Google Postmaster Tools Manage Domains screen with a verified domain and user access controls.
- Confirm the new owner: Sign out, sign back in with the new account, and confirm you can manage users for the verified domain.
- Verify a backup owner: Repeat DNS verification from a second company-controlled Google account because each owner needs a separate verification record.
- Review stale tokens: Map every Google verification record to its account and any other Google services that depend on it before cleanup, then follow your DNS and security policies.
- Avoid personal recovery: If the old owner used a personal Gmail account, do not try to recover it. Re-verify with company-controlled DNS instead.
Give your team access that survives turnover
Once you regain ownership, set up access to prevent the same problem. Verify each owner account separately in DNS, then use Manage users for people who only need dashboard access. For detailed team access steps, use the share access workflow.
|
|
|
|---|---|---|
Verified owner | Two employees | Separate DNS token for each account |
Dashboard user | Deliverability team | Added through Manage users |
DNS administrator | IT or platform team | Publishes account-specific tokens |
Agency | Named Google accounts | Read access where sufficient |
A compact access plan for Google Postmaster Tools after recovery.
Do not make a single shared login the only owner. Shared logins create weak audit trails and unclear accountability. Use named company-controlled owner accounts with documented DNS tokens. If an agency or contractor needs access, grant read access where sufficient and review it during offboarding. Enable 2-Step Verification and maintain company-controlled recovery options for each owner account.
Access resilience target
A simple threshold for deciding whether your Postmaster Tools ownership setup can survive an account departure.
Good
2+ owners
At least two current verified owners with separate tokens and a documented offboarding process.
Warning
1 owner
One verified owner plus delegated users. Recovery still depends on one account.
Critical
0 current
Only a departed manager owns the domain. DNS re-verification is urgent.
Use Postmaster Tools with email authentication monitoring
Google Postmaster Tools shows delivery and compliance data for personal Gmail accounts. During access recovery, check whether DMARC, SPF, and DKIM pass across real mail streams. Ownership handoffs often expose related gaps such as old senders or stale DNS records. The Domain and IP Reputation dashboards are absent from v2, as described in Google's v2 transition guidance.
Suped is our DMARC and email authentication platform. During a Postmaster Tools handover, it can keep DMARC aggregate reports available and map SPF and DKIM results to sending sources while Google access is being restored.
Suped DMARC dashboard showing email volume, authentication health, and source breakdown
For a quick outside-in check during recovery, run the email tester with a real message, then use the domain health checker to validate the domain's public authentication posture. For ongoing reporting after access is restored, Suped's DMARC monitoring keeps daily authentication evidence available to the team.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
Postmaster Tools and authentication monitoring answer different questions. Keeping both available prevents a lost dashboard login from hiding DNS or authentication problems during a migration, domain change, or sender rollout.
What to check after access returns
- Gmail trend: Confirm Compliance status, user-reported spam rate, and authentication trends are visible in the available dashboards.
- Authentication: Check SPF and DKIM pass rates by source. Investigate unfamiliar sources and repair legitimate senders that fail authentication.
- Policy: Review the DMARC policy before changing enforcement during access recovery.
- Ownership: Record who can change DNS, who can add users, and who reviews access quarterly.
Views from the trenches
Best practices
Verify a new owner with DNS before touching old records or delegated access settings.
Keep two active owners documented, with each Google token mapped to a current person.
Use only the TXT or CNAME record Google supplies, and preserve active verification tokens.
Common pitfalls
Deleting the old token first can remove a fallback before the replacement owner works.
Treating viewer access as ownership delays recovery and blocks team access changes.
Using one personal Google account creates the same handoff problem during turnover.
Expert tips
Store verification purpose, owner, date, and ticket ID next to the DNS record itself.
Check the live DNS answer before blaming Google for a failed verification attempt.
Review access after every agency, vendor, or deliverability team member offboarding.
Marketer view
Marketer from Email Geeks says only owner-level access can delegate users, so the fastest fix is to verify the domain again with a new DNS token.
2024-09-06 - Email Geeks
Marketer view
Marketer from Email Geeks says a domain can have more than one verified owner, which makes re-adding the same domain from a new account a practical recovery path.
2024-09-06 - Email Geeks
Document ownership after recovery
After recovery, record who owns each account, which DNS record verifies it, when access was reviewed, and what happens during offboarding. That record turns future access recovery into a documented DNS change instead of an account search.
