Licenses, editions and billing

Dana Leclair, Birchline's CFO, joins the sixth session with the reseller's quote in a folder and one question: "Are we paying for the right thing?" The contract covers about 1,100 people, but they do very different work. A buyer at head office lives in Sheets and Meet all day; a store associate checks a shift schedule and reads announcements on a shared tablet. Owen's job today is to understand Workspace editions and licensing well enough to answer Dana, and to make sure the console assigns the licenses Birchline has paid for to the right people.

Editions and what they decide

Google sells Workspace in editions, sometimes called plans or SKUs. Each edition includes a set of services, storage, security and management features, and a price per user. Editions fall into families aimed at different organizations: Business editions (Starter, Standard and Plus) for small and medium businesses; Enterprise editions (such as Enterprise Starter, Standard and Plus) for larger organizations with more security, compliance and management needs; Frontline editions for staff who work mainly on mobile devices or shared computers in stores, warehouses, clinics and factories; and Education and nonprofit editions with their own terms. Google adjusts the lineup and features from time to time, so administrators check the current comparison on Google's site rather than relying on memory.

Two facts about editions decide a lot. First, Business editions have a maximum number of users, which Google documents as 300 per account. An organization with 1,100 staff cannot put everyone on Business editions; it needs Enterprise editions (with no such cap), possibly mixed with Frontline. Second, the features an edition includes decide what admins can configure. Vault, advanced endpoint management, data regions, context-aware access and security-center features appear in some editions and not others. An exam scenario that asks why a setting is missing from the console often has the answer "the edition does not include it."

Gemini in the editions

Generative AI features used to be sold as a separate add-on. Since early 2025, Google has included Gemini features in its Business and Enterprise editions and stopped selling the Gemini add-on; billing for the old add-on ended after January 31, 2025. Which AI features a user gets still varies by edition, and administrators can turn the Gemini app, NotebookLM and individual AI features on or off for OUs and groups. GCP-211 covers those settings. For licensing, the point is that Birchline does not need a separate AI license for its Enterprise users, but it does need to check what the Frontline edition includes before promising AI features to store staff.

Birchline's license mix

With the help of the reseller, Sofia and Dana settle on a mix. About 300 people, head office staff, warehouse office staff and the 40 store managers, get Enterprise Standard. About 800 store and warehouse floor staff get Frontline Standard, because they need email, Chat, Calendar, a little storage and mobile access but not a full desktop toolset. Former employees whose mail must be kept for seven years get Archived User licenses (about 60 in the first year), so that Vault can keep their data without a full license each.

Dana wants to see the money. Owen writes a small model with illustrative prices; the real figures are in the reseller's quote, which is confidential.

# Illustrative monthly license cost for Birchline's planned mix (US dollars per user per month).
# Real prices come from the reseller's quote; these figures are for planning only.
plan = [
    ("Enterprise Standard", 300, 27.00),
    ("Frontline Standard", 800, 5.00),
    ("Archived User", 60, 4.00),
]
total = 0
for edition, seats, price in plan:
    cost = seats * price
    total += cost
    print(f"{edition:20} {seats:4} seats x {price:6.2f} = {cost:10,.2f}")
print(f"{'Monthly total':20} {'':26}{total:10,.2f}")
print(f"{'Annual total':20} {'':26}{total * 12:10,.2f}")
everyone_enterprise = (300 + 800) * 27.00 + 60 * 4.00
print(f"If all staff had Enterprise Standard: {everyone_enterprise * 12:,.2f} a year")
print(f"Saving from the frontline mix:        {(everyone_enterprise - total) * 12:,.2f} a year")

Enterprise Standard   300 seats x  27.00 =   8,100.00
Frontline Standard    800 seats x   5.00 =   4,000.00
Archived User          60 seats x   4.00 =     240.00
Monthly total                                   12,340.00
Annual total                                   148,080.00
If all staff had Enterprise Standard: 359,280.00 a year
Saving from the frontline mix:        211,200.00 a year

The model makes the case for the mix clearly: putting frontline staff on the knowledge-worker edition would cost more than twice as much for features most of them would never use. Dana's follow-up question is the right one: "What happens if a store associate becomes an assistant manager?" The answer is a license change, which brings us to how licenses are assigned.

Assigning licenses

A user can use a Workspace service only if they hold a license that includes it. Licenses are managed in the console under Billing (subscriptions and license settings) and on each user's page. There are two ways to assign them.

Automatic license assignment gives every new user in an OU a license of a chosen edition when the account is created or moved there. It is set per subscription and per OU, so Birchline sets Enterprise Standard automatically for /Head office, /Stores/Store managers and /Warehouses/Warehouse office, and Frontline Standard for /Stores and /Warehouses. Because synchronization (lesson 7) places users in OUs from Active Directory data, a new store associate will receive the right license without anyone touching the console. Automatic assignment is turned off for /Admin accounts and /Service accounts, which need no Workspace services.

Manual assignment gives or removes a license for a specific user, from the user's page or by CSV. It is used for exceptions. If the account runs out of licenses, new users are created without one and cannot use services until a license is available, which is a common cause of first-day complaints.

Licenses follow policy, not people. When Priya Shah moves from a store to the head office e-commerce team, synchronization moves her account from /Stores to /Head office/E-commerce, and automatic assignment can switch her license to Enterprise Standard. Her mail and files stay with her account. Owen checks how a license change affects storage before approving such moves, because moving from a larger to a smaller storage allowance can leave a user over quota.

Subscriptions and payment plans

Behind the licenses is the subscription, the commercial agreement for each edition. Google offers two main payment plans, and the choice affects how licenses can change during the year.

Birchline buys through a reseller on an annual plan for its stable head office and store manager licenses. Because the stores hire about 120 seasonal staff for the holiday period, Sofia asks the reseller whether a portion of Frontline licenses can be on a flexible plan. That request is a commercial question, not an admin one, and its answer depends on the reseller contract.

In the console's Billing area, administrators with billing privileges can see subscriptions, license counts, invoices (when billed by Google) and payment settings. Billing access is powerful, so Birchline gives it to Sofia's super admin account and a billing-only admin role for Dana's finance team (lesson 9).

Watching license use

Licenses cost money every month, so unused ones are waste. Owen schedules a monthly review with Dana's team, using the console's license and user reports.

The review looks for three things: licenses assigned to suspended users who have left (suspension usually keeps the license, so leavers should be deleted or archived after data transfer); licenses assigned to accounts that have not signed in for a long period, which may belong to people who left without being offboarded; and editions that do not match the job, such as a store associate still on Enterprise Standard months after leaving head office. Reports in the console show last sign-in times and license assignments, and they can be exported to Sheets for review.

Data regions and licensing

Teresa raises a question that depends on the edition: where will Birchline's data be stored? Workspace offers a data regions policy, available in specified editions, that lets administrators choose where certain data at rest is stored for an OU or group. Google's documentation lists the supported locations as the United States and Europe, with no preference as the default. For Birchline, a United States data region is possible for OUs that need it, and the privacy team decides whether to set one; customer data in Birchline's own Google Cloud projects stays in its US regions as planned in earlier courses. GCP-212 covers data regions in detail.

Trials and the first licenses

Before signing, Birchline's IT team used a trial, which Google offers for a limited period with a small number of users. Trials let an organization verify its domain, test settings and migrate a few mailboxes before buying. When the trial converts to a paid subscription, the settings and data remain. Because Birchline's domain was already in a Cloud Identity account, the reseller added the subscription to that account directly, and the trial work carried over.

Licenses also affect storage. Workspace editions include pooled storage for the organization, and administrators can set storage limits for OUs or groups so that one team cannot use the whole pool. Frontline editions include much less storage per user than Enterprise editions, which suits staff who rarely save files but matters when someone moves between them. Owen adds storage use to the monthly license review so that surprises are caught early.