GAM for Google Workspace admins: a command line that replaces clicking
command line management for Google Workspace
At a glance
- What is it?
- GAM is a Python command line tool for Google Workspace admins, distributed three ways and pinned hard. It suits admins who script domain changes, and it is the wrong shape for anyone who wants a UI.
- Who is it for?
- Adopt GAM if you administer a Google Workspace domain and want repeatable, scriptable changes instead of console clicks. Skip it if you need a graphical interface, or if you cannot live with a Python tool that pins its fourteen direct dependencies to exact versions and expects you to keep them current.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.
Star history
- GAM-team/GAM4,410 ★ · +98
| Repository | 2026-09-23 | 2026-11-21 |
|---|---|---|
| GAM-team/GAM | 4.3k | 4.4k |
98 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The admin console makes bulk domain changes a click problem
Google Workspace administration happens in a browser, and browser administration does not scale past a few dozen users. GAM exists to turn that into a command you can put in a script, and the project states its audience plainly in one line: command line management for Google Workspace admins. The reader is a Google Workspace admin who wants to manage domain and user settings from a shell.
The scope is domain and user settings, not the rest of Google Workspace. There is no web UI, no daemon, and no service to deploy. GAM is invoked per command, so the natural home for it is a provisioning script or a change window rather than a person sitting at a desk.
Three install paths, each with its own failure surface
Linux and macOS get a single shell line that downloads, installs and starts setup in one go:
bash <(curl -s -S -L https://gam-shortn.appspot.com/gam-install)That convenience is also the risk. The command pipes a remote script into bash, so trust in that appspot endpoint is part of installing the tool. Windows has no equivalent shell line; the project points you at the EXE Installer on the project's GitHub Releases page and tells you that running it starts setup.
The third path is the one to use if you already manage Python environments. GAM ships as a package named gam7, installable with pip:
pip install gam7Pick the pip route when you want the tool inside a virtualenv or a pinned requirements file. Pick the installer route when you do not.
pyproject.toml pins all fourteen dependencies to exact versions
The packaging metadata is unusually strict. Dependencies are written as equality constraints rather than ranges: arrow==1.4.0, chardet==7.6.0, cryptography==50.0.2, filelock==4.2.0, google-api-python-client==2.201.0, google-auth==2.62.0, google-auth-httplib2==0.4.4, google-auth-oauthlib==1.5.0, modern-httplib2==1.32.1.post1, lxml==6.1.3, passlib==1.7.4, pathvalidate==3.3.1 and pysocks==1.7.1, plus distro==1.9.0 on Linux only. Nothing is left to the resolver.
That buys reproducible installs and predictable API behaviour against Google, which matters for a tool holding admin credentials. It also means you inherit every one of those pins as an upgrade obligation, and conflicts are yours to resolve when another package in the same environment wants a different google-auth. An optional yubikey extra pulls in yubikey-manager==5.9.2 only if you ask for it.
The package is gam7, the command is gam, the code lives under src
The names disagree on purpose, and a skim will miss it. pip install gam7 gives you a console script named gam, registered in pyproject.toml as gam = "gam.__main__:main". The importable package is gam, and the build target packages = ["src/gam"] places it under a src layout with hatchling as the backend. Version numbers are dynamic and read from src/gam/__init__.py.
Concretely, an environment pinned around a requirements file has to carry the name gam7 while every script, cron job and CI step invokes gam. Get that mismatch wrong and the failure is a missing binary rather than a clear import error.
Python 3.14 is the newest interpreter the metadata claims
requires-python is >=3.10, so the floor is easy to clear. The classifiers stop at Programming Language :: Python :: 3.14, listing 3.10 through 3.14 individually and nothing above it. On a machine running a newer interpreter, pip will install it anyway, since the constraint is a floor, but no classifier asserts that the combination was declared.
Everything runs from that one entry point, including the setup wizard the installer hands you on first run.
Where the README runs out: rollback, dry runs and bulk reporting
The quick start ends after setup begins. The README does not document a rollback command, a dry-run flag, or how to pull a bulk report back out of the API. Detailed usage lives in the GitHub Wiki, which is where you should look before planning an unattended change.
Support runs through a Google Groups mailing list, a public Google Chat room, and two named maintainers, Jay (James) Lee and Ross Scroggs. The repository's last push was on 2026-11-02, with version 7.50.00 published on 2026-10-31, so change volume is high. That is good for API drift and bad for pinning your own dependencies to a moment in time.
The real alternative is the Admin console itself, or your own API script
Compare GAM against the two things it displaces. The Admin console is a browser UI with per-user confirmations and an audit trail built into Google; its advantage is reviewability before each change, and its cost is the reason GAM exists. A hand-written script against the Admin SDK Directory API with google-api-python-client and google-auth is the closer comparison, since GAM depends on those same libraries.
The difference is scope and surface. Your own script carries only the calls you wrote. GAM ships the whole command set, the OAuth flow and the credential handling, which is what makes a one-off admin action practical. You give up the ability to see the logic without reading the tool.
Editorial conclusion
Adopt GAM if you administer a Google Workspace domain and want repeatable, scriptable changes instead of console clicks. Skip it if you need a graphical interface, or if you cannot live with a Python tool that pins its fourteen direct dependencies to exact versions and expects you to keep them current. Before anything else, run the pip route in a throwaway virtualenv and confirm the setup wizard completes on your machine, because the one-line installer hides all of its failures behind a piped curl. Then check your interpreter version against requires-python, and read the wiki page for the specific command before you run it against a production domain.
Frequently asked questions
What is gam gam?
It is GAM, the command line tool for Google Workspace admins. It manages domain and user settings from a shell instead of the browser admin console, and it is written in Python.
What does GAM stand for?
The project's own support links resolve to Google Apps Manager, the name of the tool and its Google Groups mailing list.
Is GAM free to use?
Yes. It is released under the Apache License 2.0, so there is no paid tier and no licence fee for administrators.
What is the latest version of GAM?
Version 7.50.00 is the most recent release listed, published on 2026-10-31, after v7.49.05 and v7.49.04 on 2026-10-29.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/gam-team-gam)Star history chart for your README
[](https://hysenlabs.com/projects/gam-team-gam)Was this useful?