Firebase Authentication – Token Service API Disabled and Missing IAM Permissions in AI Studio Starter Tier

Hello Google AI Studio Team,

I am developing a multi-tenant restaurant ordering platform called AJ2M — MandaJá using Google AI Studio Build mode.

The Firebase project was automatically provisioned by Google AI Studio.

Project ID: yarling-passkey-llll..

Project Number: 8522753278..

Firestore Database ID: ai-studio-aj2mmandaj-bffdbadc-da21-4c10-b49b-edd4f6fe9a..

Firestore Region: europe-west2

Our application uses Firebase Authentication (Google Sign-In) and Cloud Firestore.

We are experiencing the following error:

auth/token-service-api-has-not-been-used-in-project-852275327899-before-or-it-is-disabled

When attempting to enable the Token Service API (securetoken.googleapis.com) in Google Cloud Console, we receive:

Missing required permission: serviceusage.services.enable

The project appears to be managed by Google AI Studio, and our account does not have sufficient IAM permissions to enable this API.

Our concern is that Firebase Authentication cannot reliably refresh authentication tokens, affecting access to Cloud Firestore.

We would appreciate clarification on the following:

  1. Is the Token Service API expected to be enabled automatically for Firebase Authentication projects provisioned by AI Studio?

  2. Is this a known limitation of the Google Cloud Starter Tier?

  3. Can the Google AI Studio team enable this API or resolve the missing IAM permission for our project?

  4. Is there an officially supported solution that does not require upgrading to a paid Google Cloud billing plan?

  5. Can we continue using Firebase Authentication and Cloud Firestore reliably under the Starter Tier?

We would strongly prefer to preserve our existing Firebase project and Firestore database rather than migrate our application and data to another project.

Thank you for your assistance.

Google buffed their entire auth ecosystem a few weeks ago, enforcing stricter management on users, specially with Firebase Admin SDK APIs and keys. People forget all the time the “zero trust” thinking when dealing with sensitive stuff… backdoors open everywhere.

The error you’re getting says its clearly: The token service API was never used (now is disabled by default) or has been disabled on purpose (either by you or automatically by Google on safety grounds). You need to enable it and give proper permissions to users in the organization.

Since each case has it’s own particularities, and Google has a complex administration service, my suggestion is take the issue to Gemini exactly as you posted it here and to ask Gemini to guide you on the permissions issue. Answer to check find help in Gemini might sound “lazy” but trust me: I ran with this wall 3 times in a row with different accounts and Gemini guided me to sail Google Cloud’s maze in minutes.

Cheers!

Hello Google AI Studio Team,

I would like to follow up on this issue.

After further investigation, it appears that my account does not have the IAM permissions required to enable securetoken.googleapis.com.

I would strongly prefer to preserve my existing Firebase project and remain on the Starter Tier if possible.

Could a Google AI Studio engineer or platform administrator please:

1. Verify the current status of securetoken.googleapis.com in project 8522753278..

2. Check whether the project provisioning system incorrectly disabled or failed to activate this required Firebase Authentication service.

3. Confirm whether the Starter Tier intentionally restricts this API.

4. If this is a platform-side issue, restore the required API or permissions without requiring project migration or billing activation.

I would also appreciate confirmation of whether linking a Cloud Billing account actually grants the necessary IAM permissions in AI Studio-provisioned projects. I do not want to introduce billing charges without a verified technical reason.

Project ID: yarling-passkey-llll2

Project Number: 8522753278..

Preserving the existing Firestore database, Firebase Authentication users and all application data is essential.

Thank you.

Hello,

Thank you very much for taking the time to share your experience and for also reaching out to me by email.

I appreciate your recommendation to use Gemini to investigate the IAM permissions issue.

I have already followed the suggested approach and confirmed that my Google account cannot enable `securetoken.googleapis.com` because it lacks the `serviceusage.services.enable` permission.

My main concern is that this project was provisioned through Google AI Studio Build mode, and I would like to preserve the existing Firebase project, Firestore database, authentication users and all application data.

I would prefer not to create another project, migrate the database or activate paid billing without first confirming that these steps are genuinely necessary.

Since you mentioned that you encountered a similar issue with different accounts, may I ask:

1. Did you manage to resolve it without linking a Cloud Billing account?

2. Did Google AI Studio or Google Cloud support have to intervene?

3. If billing linkage was necessary, did it actually restore the required IAM permissions?

Any additional guidance or relevant experience would be greatly appreciated.

Thank you again for your assistance!

Hello,

Thank you for your email and for taking the time to share the same guidance with me.

I followed your recommendation and used Gemini to investigate the IAM permissions issue.

The analysis confirmed that my account is missing the serviceusage.services.enable permission required to enable [securetoken.googleapis.com](http://securetoken.googleapis.com).

However, since this Firebase project was automatically provisioned through Google AI Studio Build mode, I am not sure whether this is a standard IAM restriction or a limitation related to the managed project environment.

I have now posted a follow-up in my original Google AI Developers Forum thread, requesting clarification and possible assistance from the Google AI Studio team.

My priority is to restore the existing Firebase project without migrating the database, losing authentication users or introducing unexpected billing costs.

If you have any additional insight into how to resolve this issue while keeping the project on the Starter Tier, I would sincerely appreciate your advice.

Thank you again for your time and support.

Best regards

A sábado, 31/10/2026, 23:08, gershu <notifications@discuss.ai.google.dev> escreveu:

Hello @AJM_TECNOLOGIA ,

Starter Tier projects are Google-managed, so additional APIs like securetoken.googleapis.com cannot be enabled directly while on the Starter Tier.

To keep your existing application, Firebase Authentication setup, and Firestore data, please try the below steps:

Hello,

Thank you again for your guidance.

Before proceeding with the suggested Starter Tier upgrade, I would appreciate clarification on a few points:

  1. Is linking a Cloud Billing account the only supported way to enable securetoken.googleapis.com for an AI Studio-provisioned Starter Tier project?

  2. Can the project remain on the Firebase Spark plan after linking Cloud Billing?

  3. Will upgrading preserve all existing Firebase Authentication users, Firestore data, database configuration and application resources?

  4. Is there an alternative to enabling this API without linking a Cloud Billing account?

  5. Does linking Cloud Billing introduce any costs by itself, even if the project remains within the free usage quotas?

I have another Firebase project on the Spark plan, with no Cloud Billing account linked, where the Token Service API is already enabled.

This makes me wonder whether there is a difference in project provisioning or API management between the two projects.

My priority is to preserve the existing AJ2M — MandaJá project and avoid unnecessary billing or migration.

I would appreciate confirmation from the Google AI Studio team or an official Google Cloud representative before making any changes.

Thank you for your help.

Hello,

Thank you for taking the time to explain the Starter Tier limitations and suggest upgrading the project to a Standard project by linking a Cloud Billing account.

I appreciate your guidance. Before proceeding, I would like to clarify a few important points to avoid unnecessary billing costs or changes to our existing infrastructure.

Our project, AJ2M — MandaJá, already has Firebase Authentication and Cloud Firestore configured, with existing users, data, and application functionality that we need to preserve.

The main issue is that Firebase Authentication is returning the following error:

auth/token-service-api-has-not-been-used-in-project-852275327899-before-or-it-is-disabled

When attempting to enable the Token Service API, Google Cloud reports that our account does not have the required serviceusage.services.enable permission.

I have also investigated another Firebase project of mine, GINGA FUTSAL, which is on the Spark plan, has no Cloud Billing account linked, and has the Token Service API enabled. This makes me wonder whether there is a difference in project provisioning or management between these two projects.

Could you please clarify the following?

  1. Is upgrading a Starter Tier project to a Standard Google Cloud project through the Upgrade option the only supported way to enable the Token Service API in this situation?

  2. Does linking a Cloud Billing account automatically change the Firebase pricing plan from Spark to Blaze, or can the project remain on Spark while having a Cloud Billing account linked?

  3. Can the project be upgraded without migrating or recreating Firebase Authentication users, Firestore databases, existing documents, and other project resources?

  4. Is there any alternative for enabling the required API without linking a personal Cloud Billing account, such as requesting the necessary permissions or having Google support review the project?

  5. If Cloud Billing is required, are there any billing implications simply from linking the account, even if the application remains within the Firebase free usage quotas?

I am currently developing this project from Angola and only have a local Multicaixa bank card, which may not be accepted by Google Cloud Billing. Therefore, I need to understand the available options before making any billing commitment.

My intention is not to avoid paying for services when necessary. I simply want to complete the application, validate it with a few real restaurant customers, and avoid activating paid infrastructure before it is genuinely needed.

I would greatly appreciate any official Google documentation or confirmation from the appropriate support team regarding these points.

Thank you again for your help.

Best regards,

Sai Deepika Kandiganti <notifications@discuss.ai.google.dev> escreveu (segunda, 2/11/2026 à(s) 15:38):

Hello @AJM_TECNOLOGIA ,

We have made some changes, so this issue should now be resolved without upgrading your project or linking a Cloud Billing account. Could you please start a new chat in your app, try again, and let us know if the issue still exists?

For your other questions:

  • Unlike Firebase Spark projects owned directly by your account, Starter Tier projects are managed by Google and have APIs enabled centrally.
  • Linking a Cloud Billing account moves a project from Spark to the Blaze plan, with no flat fee as long as usage stays within no-cost limits.
  • Upgrading a Starter Tier project keeps your existing Firebase Auth users and Firestore data in place, after which you can enable the Token Service API using the second step shared above.

Hello everyone,

First, please accept my apologies for the delayed response. I have been away from this discussion for a while.

I would like to sincerely thank both contributors for taking the time to investigate and share their suggestions.

A special thank you to the team member who followed up on November 5 and confirmed that changes had been made to resolve this issue without requiring a project upgrade or linking a Cloud Billing account.

This is very encouraging news, especially because our main priority is to preserve the existing AJ2M — MandaJá Firebase project, including its Authentication users, Firestore database and application data, while keeping the project within the free usage options.

I will now start a new chat in Google AI Studio, as suggested, and carefully retest Firebase Authentication and Firestore connectivity.

Once I have the results, I will return to this discussion and share my findings.

Thank you again for your time, support and assistance. I really appreciate it!

Hello everyone,

First, please accept my apologies for the delayed response. I have been away from this discussion for a while.

I would like to sincerely thank both contributors for taking the time to investigate and share their suggestions.

A special thank you to the team member who followed up on November 5 and confirmed that changes had been made to resolve this issue without requiring a project upgrade or linking a Cloud Billing account.

This is very encouraging news, especially because our main priority is to preserve the existing AJ2M — MandaJá Firebase project, including its Authentication users, Firestore database and application data, while keeping the project within the free usage options.

I will now start a new chat in Google AI Studio, as suggested, and carefully retest Firebase Authentication and Firestore connectivity.

Once I have the results, I will return to this discussion and share my findings.

Thank you again for your time, support and assistance. I really appreciate it!

A quinta, 5/11/2026, 07:26, Sai Deepika Kandiganti <notifications@discuss.ai.google.dev> escreveu: