An organization may be able to regain control of its Google Workspace account even when the only administrator has died, become seriously ill or left without handing over access. Google has an administrator-recovery process and, for some active users who cannot contact an administrator, a route to request promotion after proving control of the organization's domain. Neither process should be treated as instant or guaranteed.
The best protection is to arrange separate, trusted administrators while the organization can still manage its account. For a small clinic, community group or family business, that can determine whether staff can continue receiving email, managing shared files and handling billing during an emergency.
Why an ordinary staff login may not be enough
Google Workspace is the organization-managed version of services such as Gmail, Drive and Calendar. It uses an Admin console to manage users, security settings, service access and other account arrangements. A super administrator is a user with especially broad control of that console.
A staff member may still be able to read their own messages while having no permission to reset a colleague's account, assign new administrators or deal with certain organization-wide settings. Google lists the super administrator's privileges separately from the permissions available to ordinary users and more limited administrators.
This matters when one person manages the service for everyone. The group may know its domain name, pay the invoices and operate the website, but still lack the Google Workspace permissions needed for a particular change. Control over the domain's DNS records—technical settings used to direct internet services—can become part of proving authority, yet it is not the same as already possessing a working super-admin login.
If someone else is already a super administrator
First establish whether there is another authorized super administrator. A second administrator may be able to reset the unavailable administrator's password or assign appropriate privileges to another person, using the Admin console. That is generally a safer starting point than asking staff to use the absent person's credentials or attempting repeated login guesses.
The surviving administrator should review the organization's current staff roles, recovery methods, billing notifications and accounts that depend on the absent administrator's personal phone or email address. Changes should follow organizational authorization and internal privacy controls. The person managing the crisis is not automatically entitled to read an individual's personal messages, medical information or unrelated private data.
Google recommends more than one super administrator, managed by different people. It also cautions against shared administrator logins because a shared account makes it difficult to tell who performed a change. Its administrator security guidance recommends using separate accounts for super-admin duties and ordinary daily work.
If no administrator can be reached
Google's administrator access recovery guidance has a separate path for an active Google Workspace or Cloud Identity user who cannot contact the administrator. The user can open Google's official recovery form, supply the organization's email domain, choose the option identifying an unreachable administrator and follow the verification instructions. Google may require proof of domain control through a DNS record.
The documented flow generates a support reference, asks for verification and provides a request for user promotion. Google says it will contact existing administrators and may promote an eligible user when they are inactive and unresponsive. This is not a general invitation for outsiders to take over an organization's accounts. Google specifies that only active accounts can be promoted through this route, and its checks are designed to assess the request.
If your organization is in this situation, begin by confirming the exact service and domain. Locate current invoices, the existing staff account and the organization-authorized person responsible for the request. Follow Google's current directions from an official google.com service. A business owner, board officer or executor who is not an active Workspace user should not assume the same user-promotion option applies to them.
The technical step may involve a DNS TXT or CNAME record. This is a text entry added at the domain's DNS host so Google can check control of the domain. Someone who edits DNS for the first time should coordinate with the domain registrar or qualified administrator; changing unrelated records can disrupt the website or email. Google notes that DNS verification may take time and that additional checks can apply. The full request may remain pending while the company confirms the proper authority.
What if the person is still an administrator but cannot sign in?
Google also documents recovery routes for a legitimate administrator who has forgotten credentials or has lost a recovery device. These include account recovery and, where appropriate, verification through domain settings or support. The correct branch depends on whether the administrator is still acting, whether recovery methods were configured, and whether another super administrator is available.
Do not use the absent person's private recovery phone, personal identity information or saved passwords without proper authorization simply because the organization needs its email. When an administrator has died, contact the provider using the organizational route rather than impersonating the deceased user. If an account was created by an outside contractor, establish what service the contractor actually controls and whether a reseller agreement applies. This may require contractual or legal review as well as a Google support request.
Put continuity arrangements in place before a crisis
An organization that currently has access can reduce the risk through a short administrative review. In Google Admin console, an authorized super administrator can open Directory, select Users, open a trusted user's profile, and review Admin roles and privileges. Google's current role-assignment instructions show how to assign the Super Admin role where appropriate. Some organizations use additional approval controls, and changes in privileges may take time to take effect.
Appoint another qualified person only after considering the scope of access that comes with the role. A super administrator can exercise powerful controls over users and organizational services. For everyday tasks, Google's guidance favors narrower permissions where possible. A second full administrator should be accountable to the organization, use an individual account and understand what to do if the primary administrator is unavailable.
Protect both accounts with appropriate two-step verification, which requires something beyond the password to sign in. Google recommends security keys and other backup methods for administrative accounts. The person responsible for continuity should know where approved recovery procedures and spare equipment are stored; this does not mean keeping shared administrator passwords on an open spreadsheet.
Record which company manages the domain and DNS, the Workspace billing contact, any authorized reseller, and the current administrators' organizational contact information. Keep this inventory separate from secret authentication material and restrict access to people who need it. Provide a way to update the inventory when staff or vendors change. Also make sure mandatory notices and billing messages reach more than one appropriate contact, as Google recommends.
What to do when an administrator leaves or the arrangement changes
An organization should review privileges as soon as a manager, volunteer or vendor's responsibilities change. An authorized successor can check that the new administrator can sign in successfully and that recovery methods are current before removing the previous person's role. Google's role-transfer guidance follows this sequence to avoid leaving the account without an administrator.
If a staff member no longer has authority, promptly review their permissions using established organizational procedures. Preserve necessary work records and respect employee and third-party privacy. Replacing a person who has resigned is different from addressing an owner's death, but in both situations the institution needs continuity without unauthorized account access.
A personal Gmail address used by a founder may remain outside the Workspace organization. It is important not to confuse the founder's personal Google Account with the company's administered Workspace. Different recovery and deceased-account processes may apply. The same distinction holds for a domain registrar account or an external website-hosting account, which may need their own authorized contact and recovery arrangements.
Specific limits to keep in mind
Google's published procedure deals with recovering administrative access to a Workspace or Cloud Identity organization. It does not decide ownership of a business, grant a family member ownership of an employee's private correspondence, or resolve a dispute between directors or heirs. It also does not establish what happens to every subscription when invoices go unpaid; that depends on the organization's current terms and account status.
The instructions in this article were checked against Google's October 2026 support documentation. A reader should still use the current recovery flow and confirm any necessary organizational or legal authority. A continuity plan that names two trusted administrators, secures their accounts and records domain and billing responsibilities gives an organization a more reliable starting position than an emergency request made after the only administrator is gone.
Sources and verification
Primary Google documentation directly checked October 28, 2026:
- Recovering administrator access to your account — Google's page states last updated October 6, 2026.
- Security best practices for administrator accounts — last updated October 13, 2026.
- Make a user an admin — last updated October 7, 2026.
- Prebuilt administrator roles — policy guidance available at the review date.
No actual Workspace recovery form was submitted or tested for this article. Organizations should confirm the current process and applicable privacy obligations with the provider and their own advisers.