Skip to main content

​
What is this?

The Firebase Setting tab connects your platform to a Firebase project so the platform can authenticate users and deliver push notifications to web, Android, and iOS.

​
What can I do here?

  • View the current Firebase configuration (API Key, Auth Domain, Project ID, Storage Bucket, Messaging Sender ID, App ID, Measurement ID, Private Key, Client Email, Vapid Key)
  • Click Edit Settings to open a modal and enter or update all of these values
  • Turn on Require phone verification after login, and choose whether it applies to Admins, Team members, or both
  • Click Sync Providers to pull the list of authentication providers (e.g. Google, Facebook, Email/Password) enabled in your Firebase project and apply them to the platform automatically
  • See a status indicator confirming whether a Firebase configuration is active, and whether phone verification is on or off

​
How to use it

  1. Go to the Firebase Console and create a project for your platform, then open Project Settings.
  2. Inside the project, add a Web App. Firebase generates a config object for it.
  3. From Firebase Console → Project Settings → General, collect API Key, Auth Domain, Project ID, Storage Bucket, Messaging Sender ID, App ID, and Measurement ID.
  4. From Firebase Console → Project Settings → Service Accounts, click Generate New Private Key to download a JSON file. Copy the Client Email and Private Key from it — keep this file secure and never share it publicly.
  5. From Firebase Console → Project Settings → Cloud Messaging, generate a Web Push (VAPID) key if you need push notifications.
  6. Back in the platform, click Edit Settings and paste each value into its matching field, then click Save.
  7. If you later enable a new sign-in provider (e.g. Google Login) directly inside Firebase, click Sync Providers on this page instead of re-entering everything by hand — the platform fetches the enabled providers from Firebase and updates itself.
  8. Optionally, turn on Require phone verification after login and choose whether Admins, Team members, or both must verify a phone number via SMS before using the app. This requires Phone sign-in to already be enabled in your Firebase project’s console.
The "Required OAuth Scopes" card listing the four Google API scopes granted to the Firebase service account

​
Troubleshooting / Technical Notes

  • Settings saved but sign-in or notifications don’t work. The Edit Settings form doesn’t stop you from saving with blank fields (unlike the Instagram and Facebook OAuth tabs). Re-open Edit Settings and confirm the API Key, Project ID, and other values are all filled in.
  • Sync Providers seems to do nothing. If Firebase has no sign-in providers enabled yet, you’ll see a message that no saved provider configuration was found, and nothing is synced. Enable a provider in the Firebase Console first, then click Sync Providers again.
  • The Private Key and Vapid Key show only dots. These values are masked by default. Click the eye icon at the right of the field to show or hide the saved value. To change a value, click Edit Settings and re-enter it.
  • Push notifications or Firebase sign-in stop working after a key rotation. Rotate the exposed key in the Firebase Console first. Then re-open Edit Settings, paste the new privateKey and clientEmail from a freshly downloaded service-account JSON, and save. The platform can’t detect a revoked key on its own.
Last modified on October 21, 2026