Firebase Settings
Overview
The Firebase Settings page is used to connect your platform with Firebase services. Firebase is required for features such as authentication, push notifications, and mobile/web notification delivery.
Once Firebase is configured, the platform can send push notifications to users across supported environments such as web, Android, and iOS.
When Firebase Is Required
Firebase configuration is required if you want to use platform features such as push notifications, app notifications, Firebase authentication, or device-based notification delivery.
For example, if you want to send notifications from the Notifications page, Firebase must be configured first. Without Firebase setup, notifications may be created inside the platform, but they will not be delivered to user devices.
Step 1: Create a Firebase Project
Go to the Firebase Console and create a new project for your platform.
After creating the project, open Project Settings from the Firebase dashboard. This is where you will find most of the values required for your platform configuration.
Step 2: Add a Web App in Firebase
Inside your Firebase project, add a new Web App.
Firebase will generate a configuration object for the web app. From this configuration, copy the required values into the platform’s Firebase Settings page.
Step 3: Generate Firebase Admin Credentials
You will usually need values such as:
- API Key
- Auth Domain
- Project ID
- Storage Bucket
- Messaging Sender ID
- App ID
- Measurement ID
These values connect the frontend application with your Firebase project.
Firebase Console → Project Settings → General
Step 4: Generate Firebase Admin Credentials
For backend operations, the platform also needs Firebase Admin credentials.
To generate these credentials, go to:
Firebase Console → Project Settings → Service Accounts
Then click Generate New Private Key and download the JSON file.
Firebase’s official documentation states that this JSON file contains the private key and service account information required by the Admin SDK.
From the downloaded JSON file, copy the required values into the platform, such as:
- Client Email
- Private Key
- Key Pair / Service Account JSON details
Keep this file secure. Do not share it publicly or upload it to public repositories.
Firebase Cloud Messaging is required for push notification delivery.
To configure web push notifications, open:
Firebase Console → Project Settings → Cloud Messaging
From there, configure or generate the required Web Push certificates / VAPID key. Firebase uses VAPID keys to authorize web push notification requests.
This setup allows the platform to register user devices and send push notifications correctly.
After collecting the Firebase web configuration and admin credentials, open the platform’s Firebase Settings page and enter the values into the matching fields.
Once saved, the platform will use these credentials for authentication-related services and notification delivery.
Step 7: Sync Providers
The Sync Providers option is used to connect and synchronize authentication providers from your Firebase project with the platform.
In Firebase, you can enable different authentication methods such as Google, Facebook, Email/Password, or other supported providers. Once these providers are configured inside Firebase, the platform needs to be aware of them so they can be used for user login and authentication.
When you click Sync Providers, the platform fetches the list of enabled authentication providers from your Firebase configuration and updates them internally. This ensures that any login methods configured in Firebase are automatically available within the application.
For example, if you enable Google Login or Facebook Login in Firebase Authentication, syncing providers will make those login options usable inside your platform without additional manual setup.
This process helps keep your authentication system aligned with Firebase and ensures that all enabled login methods are properly integrated and ready for use.
Important Notes
Firebase credentials should be handled carefully because they connect your platform to external notification and authentication services.
The private key should always be stored securely. If it is exposed, generate a new private key from Firebase and replace the old one in the platform settings.
Last modified on April 24, 2026