The Professional Workspace Administrator certification was retired
Google retired the Professional Google Workspace Administrator examination on December 31, 2024. The official retired certification listing states that it can no longer be renewed and directs candidates to the Associate Google Workspace Administrator program. A study guide written as if the former professional examination were still bookable is misleading in October 2026. Its technical descriptions of managing accounts and services can still be useful, but the old credential must be labeled as historical.
The current Associate Google Workspace Administrator program focuses on user accounts, core Workspace services, governance, access policies, endpoints and troubleshooting. Google lists no formal prerequisite and recommends approximately six months of Super Admin experience in a test or real environment, with familiarity with relevant Business Plus and Enterprise features. Recommended experience is not an enforced eligibility requirement. Confirm the current exam guide, language and appointment rules directly with Google rather than adopting a 2024 professional-level practice test as the current syllabus.
Organize users and policies around real responsibilities
Google Workspace administration starts with identity and business structure. Organizational units can define policy scope, while groups help distribute communication and access. A user belonging to a group does not automatically mean every policy for some other organizational unit applies to that account. Administrators must understand the inheritance and exception rules supported by their actual subscription edition.
Imagine a test tenant with employees, contractors and administrators. Document who needs Gmail, Meet, shared drives and external sharing. Assign users to suitable organizational units and give groups only the permissions appropriate to their work. Observe how a controlled policy change affects two different test users. Record the intended behavior, the configuration and what actually happened.
Admin privileges also need separation. A support engineer who resets ordinary user accounts may not need the ability to change domain-wide security settings. Set up dedicated roles where supported and review privileges after role changes. An account being part of the IT team is not enough reason to grant Super Admin rights.
Manage account creation, suspension and offboarding
Account lifecycle management includes verified requests, account creation, organizational placement, license assignment, secure authentication, suspension, restoration and planned offboarding. An onboarding checklist should identify the business owner and systems needed. Preventing stale access is as important as enabling productive work.
When a person leaves, distinguish suspending sign-in from transferring business-owned files, assigning group ownership and retaining data under applicable policy. Deleting an account immediately can disrupt collaboration or create problems with legal preservation. Agree on who approves data transfers and what happens to a departed employee’s shared resources before acting.
Practice with synthetic users. Create an account, grant and test the minimum required permissions, suspend it and confirm expected restrictions. If a login fails, separate account status, authentication policy, device restrictions and service availability before changing tenant-wide settings.
Configure Gmail and investigate delivery responsibly
Gmail administration involves domain setup, authentication, routing, spam controls, user settings and possible external mail gateways. SPF, DKIM and DMARC address different aspects of sender authentication and domain policy. Successful authentication is helpful evidence but does not guarantee inbox placement, and a trusted-sounding display name does not prove a message’s origin.
When mail delivery fails, record sender, recipient, approximate time and a message identifier when available. Check routing and available mail logs, then determine whether the issue is an authentication failure, policy action, queueing or a recipient-side issue. Do not permanently disable anti-spam or security enforcement to make one test message arrive.
Review third-party application permissions that can access mail or directory data. OAuth grants can create significant risk without exposing a user’s password. Evaluate requested scopes and whether the integration is still needed, then remove excess access through the supported administrative process.
Set Drive and shared-drive access deliberately
Google Drive permission decisions involve individual files, folders, groups, sharing links and organizational controls. Shared drives can help teams keep important files accessible independently of a single employee account, but membership and external-sharing rules still require governance. A shared drive is not necessarily visible to everyone in the company.
Give a synthetic finance team a restricted shared drive and add a test collaborator with limited access. Verify what that person can view, edit and share, including what happens after group membership is removed. Do not switch to an unrestricted public link merely because one intended user was denied access. Investigate which permission boundary actually caused the problem.
Retention and electronic discovery require a separate policy assessment. A retention rule is not a backup plan, and product capabilities can vary by Workspace edition. Where regulated records or legal holds are involved, follow applicable organizational obligations and specialist guidance rather than copying generic deletion instructions.
Protect administrator accounts and devices
Security planning should address multifactor authentication, recovery methods, privileged roles, session controls, app access and endpoint management. Keep emergency access procedures tightly controlled and tested; permanent broad exemptions undermine the baseline. Verify that a security policy works for the actual target users and devices, not just for an administrator who is exempt from restrictions.
Managed laptops, personal mobile devices and shared kiosks may require different controls. A remote wipe or device restriction can be highly disruptive and should follow explicit authorization. Test proposed settings on disposable accounts and enrolled test devices before organization-wide rollout.
Audit logs and security reports help determine whether a policy was applied and whether a suspicious event needs investigation. They can have access requirements and retention delays. An unusual login is a signal for review, not proof that an account was compromised. Preserve available evidence and follow defined escalation responsibilities.
Troubleshoot by establishing the scope of the failure
When someone says Google Workspace is unavailable, identify whether the problem affects one account, one device, a network, a single service or multiple users. Document the exact error, event time and recent changes. Check official service status when a broader incident is plausible. The administrator should distinguish policy, identity, transport and application causes rather than changing unrelated settings at once.
In an authorized test, deliberately remove a collaborator from a group and observe which Drive resources become inaccessible. Re-establish approved access, then verify that users outside the group remain restricted. For Gmail, test a known sender and recipient with the relevant routing policy and preserve log evidence of delivery or rejection. These exercises teach the diagnosis process without creating production risk.
Study the active Associate program with evidence
Compare the current Google Associate Workspace Administrator exam guide with hands-on tasks you can perform in a permitted tenant: organizational units, groups, user lifecycle, mail services, shared drives, security, endpoint controls and troubleshooting. Record before-and-after states for each exercise. Practice how to undo an unintended configuration change.
The retired Professional certification remains a legitimate historical credential for those who earned it under the previous program, but it should not be presented as a current examination. The practical learning goal is to make secure, well-supported administrative decisions with verifiable evidence, not a promise of a score, job or salary.