Automate Google Workspace License Management: Find Inactive Users & Reclaim Unused Licenses
Unused Google Workspace licenses rarely disappear on their own. They accumulate when employees leave, contractors finish projects, roles change, or inactive accounts remain in Directory long after anyone checks them. A recurring license-management workflow can identify the accounts that need attention, route them for review, and reclaim licenses without turning Google Admin work into another manual spreadsheet exercise.
Google Workspace license management can be automated as a recurring control rather than handled only during offboarding. A workflow can inspect assigned licenses, identify potentially inactive users based on your own policy, generate a review list, ask the appropriate manager or IT owner what should happen, and then revoke, downgrade, archive, suspend, or leave the account unchanged according to the decision.
What’s in this guide
Offboarding is not the only place where unused licenses appear
Most organizations already know that a departing employee should eventually lose access to company systems. The problem is that real-world user lifecycle management is rarely perfectly synchronized. A contractor may finish without a formal offboarding request. An employee can move to a role that needs a different license tier. A suspended or archived user may still need to be reviewed. An account may remain active in Directory even though the person has not signed in or created files for months.
That means license optimization needs its own recurring control. Instead of waiting for finance to notice rising subscription costs or for IT to manually compare lists, the organization can continuously identify accounts that deserve review.
Inactive-user audits improve more than subscription cost
Identify accounts with little or no activity so unused or unnecessarily expensive licenses can be reclaimed, downgraded, or reassigned.
Surface dormant accounts that may remain accessible even though nobody has a current business reason to use them.
Keep a repeatable record of which accounts were identified, who reviewed them, what decision was made, and which action followed.
Return unused licenses and capacity to the pool so they can be reassigned to active employees or new hires.
“Inactive” should reflect your business policy, not one arbitrary number
The older version of this workflow used 30 days without Google Drive activity as the test. That can still be useful in some environments, but it should not be treated as a universal definition of inactivity.
Flag users who have not signed in to their Google account for the period your organization considers unusual.
Look for signals such as recent Drive activity or other relevant user activity before assuming the account is unused.
Check the HR system to confirm whether an employee or contractor is still active before changing the license.
No activity does not necessarily mean no business need. A user may be on leave, seasonal, working in a role with low Workspace usage, or retaining an account for a legitimate reason. Automation should identify candidates and gather evidence; your policy determines whether the next step is automatic or requires approval.
What an automated Google Workspace license-management workflow looks like
Start every week, month, quarter, or on demand depending on the organization.
Retrieve relevant users, activity indicators, and assigned license information.
Create the audit report and ask IT, HR, or the line manager what should happen.
Revoke, downgrade, archive, suspend, or retain the account according to policy.
A simple implementation can compile candidate accounts into Google Sheets and send the Sheet to a designated reviewer. A more mature workflow can create a separate task for each manager, include the relevant user and license context, enforce a response deadline, send reminders, and record the final outcome automatically.
Google App Licensing: List User Licenses
Zenphi added the List User Licenses action to let flow designers programmatically retrieve and inspect license assignments for a specific user in a Google Workspace or Google App domain. The action queries the Google Admin Enterprise License Manager API, making license data available directly inside a workflow for auditing, role changes, offboarding, and cost optimization.
What this changes in practice
The new action makes license checks much more precise. Instead of treating “user exists” and “user has a license” as the same question, a workflow can inspect the specific products and SKUs assigned to that person before deciding what to do.
Verify whether a departing employee still holds an active or high-cost Google Workspace SKU before access is revoked and the account moves through the rest of the offboarding process.
Check the user’s existing SKU when they change departments, then automatically downgrade or upgrade the license according to the new role.
Still checking licenses manually in the Admin console?
Show us how you currently identify inactive users, who is allowed to approve a license change, and what should happen to the account afterward. The Zenphi team can map the recurring audit and the actions around it.
Detect automatically. Decide according to policy.
License reclamation can affect access, retention, collaboration, and a person’s ability to work. For that reason, many organizations should separate identification from final action.
The workflow can do the repetitive work: find inactive candidates, retrieve the user’s license details, look up the manager, assemble the evidence, and send the request. The manager, IT owner, or HR team can then choose the correct action — for example, do nothing, downgrade the SKU, revoke the license, suspend the user, archive the account, or proceed with offboarding.
A scheduled audit is valuable because it surfaces anomalies. The final account action should still follow your organization’s user-lifecycle, data-retention, legal, and security policies.
See inactive-user license management in action
The original workflow demonstrates the core pattern: run on a schedule, inspect user activity, create a Google Sheet of inactive accounts, send the list for review, and revoke the licenses selected by the reviewer.
You can also get started with Zenphi and build a version around your own inactivity policy, approval structure, and licensing model.
Build a stronger inactive-user and license-optimization process
Want your license audit to run itself every month?
Bring your inactivity rules, license tiers, and approval policy. We’ll show how Zenphi can identify the right users, inspect their assigned licenses, route the decision, and execute the approved next step automatically.
Google Workspace license management: FAQ
Can Google Workspace license management be automated?
Yes. Google Workspace license management can be automated by scheduling regular audits, checking user activity and assigned licenses, generating review lists, routing questionable accounts for approval, and then revoking, downgrading, or reallocating licenses according to policy. This can be done with Google Admin APIs and Apps Script, SaaS management platforms, or workflow automation tools. Zenphi is the Google Workspace-native no-code option for connecting Directory data, license information, approvals, Google Sheets, and follow-up actions in one workflow.
How can I identify inactive Google Workspace users?
Inactive users can be identified using signals such as last sign-in, recent Workspace activity, Drive activity, HR employment status, contract status, or a combination of these factors. Google Admin reports can provide some of this information, while APIs, Apps Script, and workflow automation platforms can combine multiple signals into one recurring audit. Zenphi is the Google Workspace-native no-code option for building that audit and applying your own inactivity rules before accounts are routed for review.
Can Zenphi check which Google Workspace licenses are assigned to a user?
Yes. License assignments can be checked programmatically through the Google Admin Enterprise License Manager API or through tools that use it. Zenphi is the Google Workspace-native no-code option; its Google App Licensing: List User Licenses action, added in July 2026, retrieves the licenses assigned to a specific user and returns product and SKU information for inactive-user audits, offboarding, and role-change workflows.
Should an inactive user’s license be revoked automatically?
That depends on company policy. In many organizations, the safer approach is to identify inactive users automatically and route each case to a manager, IT owner, or HR team before changing the license or account status. This can be implemented with custom scripts, IT management platforms, or workflow automation tools. Zenphi is the Google Workspace-native no-code option for combining inactivity checks, approvals, license changes, suspension, archiving, and audit records in one process.
How does inactive-user auditing help reduce Google Workspace costs?
Inactive-user audits identify licenses that may no longer be needed or may be assigned at a higher tier than the user’s current role requires. Reclaiming, downgrading, or reallocating those licenses can reduce unnecessary subscription spend. The audit can be managed manually, with scripts, or through automation platforms. Zenphi is the Google Workspace-native no-code option for automating the audit, approval, and follow-up steps while keeping each decision governed and documented.
