Features

Firebase: Credentials

Connect Firebase for push notifications via service account JSON or OAuth (Beta) in the Application Platform.

On this page

Under Connections, store a Google/Firebase credential for your organization. You can then enable Firebase for apps under Features – the platform can create a Firebase project in your Google Cloud account when needed and write the configuration into generated project files.

Two paths

Path Best for Note
Service account JSON Recommended while the OAuth app is not generally available JSON key from Google Cloud / Firebase Console
Connect with Firebase (OAuth) Authorize a Google account Beta – the platform app is not yet verified for all Google Cloud users
Tip
Until OAuth is generally available, use the service account JSON path. OAuth is shown in the UI with a Beta badge.

For dynamic Firebase project creation, the service account needs folder- and billing-level permissions – not only access to a single project.

  1. Open the Google Cloud Console (or Firebase Console) and select your organization.
  2. Create a service account with at least:
    • Project Creator on the target GCP folder (resourcemanager.projects.create)
    • Billing Account User on the billing account (billing.resourceAssociations.create)
    • Permissions to enable Firebase / services (firebase.projects.update, serviceusage.services.enable)
    • Read access to list folders and billing accounts
  3. Create a JSON key and download the file.
  4. In the Application Platform under Connections → Google / Firebase → Service account JSON:
    • Name / Slug for selection in projects
    • Service account JSON: paste the full file contents
    • Firebase / GCP project ID optional – not required for dynamic creation
  5. Click Verify. The platform validates the key and reports missing permissions explicitly.

Enable Firebase on an app

  1. In the project under Features, enable Firebase and select the stored credential.
  2. Choose Folder and Billing account (loaded via the service account API).
  3. On save, the platform creates a Firebase project idempotently and stores the project IDs on the app.

If a Firebase project ID is already set on the credential or app, no new project is created.

OAuth (Beta)

  1. Choose Connect with Firebase.
  2. Authorize the Google account and then select the Firebase project.
  3. The platform stores the connection and, where possible, fills in app configs and a service account.

If the Google consent screen reports the app as unverified, stay on the JSON path until verification is complete.

What the platform does next

When Firebase is enabled for an app, the platform uses the stored credential (JSON and/or OAuth) to write configuration and push-related settings into the generated project files.

Security

  • Do not share service account JSON publicly; limit access to organization admins.
  • Rotate keys if compromise is suspected and update the entry under Connections.
  • Grant only the required IAM roles (Folder Project Creator + Billing Account User + Firebase/Service Usage).

See also