Are Gemini Enterprise subscriptions tied to the GCP project where it is setup? I understand the subscription is linked to a billing account which makes me assume that multi-project access can be setup meaning if i have a Gemini subscription with 25 standard licenses I can assign 10 licenses to Project A and remaining 15 licenses to Project B but that doesn’t seem to be the case in reality. Another issue I am running into is that I am unable to create a brand new GE subscription in a GCP project. No errors but the subscription is not created, error mentions “subscription already exists” which is the case but that was from another project.
The whole relation between GCP Project, Gemini Enterprise subscriptions, licenses is confusing and does not work as expected. Also the subscription id from “Manage subscriptions” page does not match with what is seen in the “Manage users” page (table which lists subscriptions)
Hey, yeah I’ve seen this same confusion come up quite a lot with GCP + Gemini setup.
What you’re describing actually makes sense in a messy way — it feels like subscriptions, billing account, and project-level access should be cleanly separable, but in reality Google has tied some parts globally and some per-project, which creates this weird mismatch.
I faced something similar where I thought licenses could be split across projects, but later realized one subscription often behaves like a “single container” even if billing is shared. Also that “subscription already exists” ghost error is super common when switching projects.
What worked for me was:
double-checking org-level vs project-level permissions
using one central project for subscription management
and waiting a bit after changes (sync delay is real)
Not sure if it helps, but I’ve seen teams simplify everything under one main GCP project. Dooflix also had similar multi-project confusion in another setup.
Are you trying to separate environments or just organize teams?
Yeah, the way Gemini Enterprise ties into GCP can definitely feel confusing. In general, the subscription is linked to the billing account, but license assignment is usually scoped per project, which is why you can’t freely split or reuse the same subscription across multiple projects like that.
The “subscription already exists” message also often happens when the billing account already has an active subscription attached in another project, even if it’s not visible in the current one.
Honestly, the mismatch between subscription IDs and the “Manage users” view is something others have run into too. It’s best to double-check everything from the billing account level and ensure there’s only one active subscription setup before creating anything new.