GWS Licensing Processor

Manage Google Workspace license assignments, auditing, and optimization across your domain.

When to Use This Command

Run this command when you need to:

• Audit license assignments across your domain to identify unused or misallocated licenses
• Assign, revoke, or transfer Google Workspace licenses between users in bulk
• Generate license utilization reports for cost optimization and budget planning

Consider alternatives when:

• You need to purchase additional licenses which must be done through the Google Admin Console
• You are managing a small team of under 10 users where the Admin Console UI is sufficient

Quick Start

Configuration

Copy
name: gws-licensing-processor
type: command
category: google-workspace

Example Invocation

Copy
claude command:run gws-licensing-processor --action audit --product "Google-Workspace-Enterprise"

Example Output

Auditing license assignments...
  Product: Google Workspace Enterprise
  Domain: example.com

License Summary:
  Total purchased: 200
  Assigned: 167
  Available: 33
  Utilization: 83.5%

Inactive licenses (no login in 90+ days):
  [email protected]    Last login: 2025-11-02 (134 days ago)
  [email protected]         Last login: 2025-12-18 (87 days ago)
  [email protected]         Last login: 2026-01-05 (69 days ago)

Potential savings: 3 licenses ($54/month)
Recommendation: Revoke licenses for inactive users.

Core Concepts

License Management Overview

Aspect	Details
Products	Business Starter/Standard/Plus, Enterprise Standard/Plus, Frontline
Operations	Assign, revoke, transfer, audit license assignments per user
Auditing	Identify unused licenses based on login activity and usage patterns
Reporting	Generate utilization reports with cost projections and saving opportunities
Compliance	Ensure license types match user roles and organizational requirements

License Audit Workflow

Fetch License Inventory
        |
        v
Cross-Reference User Activity
  (login dates, usage metrics)
        |
        v
Identify Optimization Targets
  |          |           |
  v          v           v
Inactive  Over-licensed  Under-licensed
Users     Users          Users
  |          |           |
  v          v           v
Recommend Actions
  (revoke, downgrade, upgrade)
        |
        v
Generate Cost Report

Configuration

Parameter	Type	Default	Description
action	string	(required)	Operation: audit, assign, revoke, transfer, report
product	string	all	License product SKU or name to filter
user	string	(none)	Target user email for assign or revoke operations
inactive-days	integer	90	Days since last login to consider a license inactive
output	string	table	Report format: table, json, csv for export

Best Practices

1. Run monthly audits - License costs are a recurring expense. Monthly audits catch departing employees, role changes, and unused licenses before they accumulate into significant waste.

2. Match license tiers to user needs - Not every user needs Enterprise features. Downgrade users who only use Gmail and Calendar to Business Starter to save significant per-user costs.

3. Automate license assignment for new hires - Integrate the assign action with your HR onboarding workflow so new users automatically receive the correct license tier on their start date.

4. Track license trends over time - Export monthly audit reports to a spreadsheet and track utilization trends. This data supports budget conversations and helps predict when to purchase additional licenses.

5. Revoke before deleting users - When offboarding employees, revoke their license first, then transfer their data, and finally delete the account. This sequence ensures no data is lost.

Common Issues

1. Cannot revoke license from active user - Some organizations require a license for basic account access. Suspend the user first if you want to free the license while keeping the account.

2. License assignment fails with quota error - You cannot assign more licenses than you have purchased. Check available count before bulk assignment operations.

3. Audit shows stale login data - Admin Reports API has up to 48-hour latency for login data. A user marked as inactive may have logged in recently. Verify with real-time session data for critical decisions.