Why this matters
License changes affect both cost and service access. Reassigning a license without understanding automatic assignment or edition dependencies can cause unexpected service changes.
Before you begin
- Know the user's current edition and required services.
- Check whether automatic licensing is enabled.
- Confirm whether multiple subscriptions of the same service exist.
- For offboarding, preserve required data before removing services that may affect access or retention.
Step-by-step instructions
Step 1: Check automatic licensing
In the Admin console, review Billing > License settings before making one-off changes.
Why this step mattersAutomatic assignment can immediately reapply a license you try to remove.
What to look forYou should understand whether licensing is controlled globally, by organizational structure, or manually.
Step 2: Review the user's current licenses
Open Directory > Users > the user > Licenses.
Why this step mattersThis confirms what is currently assigned before any change.
What to look forRecord the starting state for high-impact changes.
Step 3: Assign a license
Turn on the required service/license and save.
Why this step mattersUsers need the correct subscription to receive edition-specific services.
What to look forThe license should appear on the user record.
Step 4: Remove a license carefully
Turn off only the license that is no longer required and verify any data/access implications first.
Why this step mattersLicense removal can affect the user's ability to access services.
What to look forThe business owner should know the impact before removal.
Step 5: Reassign between users
Remove the license from the first user and assign it to the second user after confirming availability.
Why this step mattersGoogle notes that in some cases a released license may take time before it can be assigned elsewhere.
What to look forThe second user should show the correct license before the task is closed.
Step 6: Change editions when needed
If multiple subscriptions exist, select the target subscription/edition for the user.
Why this step mattersChanging editions can change available storage and features.
What to look forVerify the user's services after the edition change.
Step 7: Reconcile license counts
Compare active users and business requirements with purchased/assigned licenses.
Why this step mattersRegular reconciliation finds unused spend and under-licensed users.
What to look forThe billing and user records should tell the same story.
What to look for when you are finished
A successful result should match the business purpose described above, use the smallest necessary access or configuration scope, and leave enough documentation that another authorized administrator can understand what was changed and why.
When to stop and contact IT
Secondary search questions this article answers
- assign Google Workspace license
- remove Google Workspace license
- reassign Workspace license
- Google Admin license management
Authoritative references
Vendor interfaces and licensing can change. Verify current platform behavior against the primary documentation below before making high-impact production changes.
Need help applying this safely?
J3 Systems Group helps small businesses and nonprofits organize, secure, document, and improve Microsoft 365, Google Workspace, devices, access, and business technology operations.
Contact J3 Systems Group