Atlas project production

Google Workspace Nightly License Assignment Automation

Keeps Google Workspace license assignments aligned to user lifecycle state through recurring GAM-based maintenance runs.

Internal-only entry. Do not publish externally without review.

Type: Field Tool
Lifecycle: Active
Last touched: 2026-03-24
Visibility: Internal

Purpose

Assign and remove Google Workspace licenses so lifecycle changes do not rely on repeated manual admin work.

Current state

Production maintenance exists through `license-manager.sh --run-presets`, with a recurring Sunday run supporting ongoing license hygiene.

Next step

Capture alerting, rollback steps, and the live production host for the preset run.

Interfaces

Inputs

user lifecycle state
license rules and presets
OU and account data

Outputs

license assignments
license removals
maintenance logs

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Contributes in this stage.

Human Interfaces

Not in scope.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

Google Workspace is canonical for final license state.
Lifecycle rules and preset definitions determine intended license assignments.

Safe handling

Protect GAM credentials and config files.
Keep user-level license reports internal.

Operational notes

Reliability posture

Recurring preset runs keep drift low, but rollback and alerting are still lightly documented.

Observability

script output
GAM command results
preset run history

Security and privacy

Confidential identity and license-state data; keep admin credentials and logs restricted.

Dependencies

Upstream

Google Workspace Admin access
license policy rules
GAMADV-XTD3

Downstream

account readiness
license cost control

Ownership

Owners

Technology Services, Josh Barton

Users

Technology Services, Josh Barton (owner)

Google Workspace Nightly License Assignment Automation

Operational Notes

The registry ties the workflow to license-manager.sh and preset-driven GAM operations.
Cron evidence currently points to a Sunday 02:00 recurring preset run even though the business intent is nightly or recurring hygiene.
Failure leads to access delays or license waste rather than data corruption.

Registry Alignment

Mapped registry entry: INT-008
Registry clarified: this is a real recurring admin automation with a concrete script and schedule, not only a licensing policy idea.
Validation gaps: Confirm the current production host, failure-notification path, and rollback procedure for incorrect assignments.