Connecting Firebase
How Firedeck connects to your Firebase projects using Google sign-in and granular OAuth scopes.
Firedeck connects to Firebase entirely through your own Google account. There is no separate Firedeck account, no API key to paste, and no service-account file to upload.
How the connection works
When you sign in, Firedeck receives an OAuth access token from Google’s sign-in SDK. Every request Firedeck makes goes directly from your device to Google’s first-party Firebase and Google Cloud REST APIs, authenticated with that token. Nothing is routed through a Firedeck server.
Granular permissions
Firedeck requests one OAuth scope per capability, so Google’s consent screen shows a granular checkbox list. You can approve only the scopes you want; declining one simply makes that feature unavailable.
| Capability | What it allows |
|---|---|
| Sign-in baseline | Your name, email, and profile |
| Firebase (read) | List projects, apps, and configuration |
| Firestore | Browse and edit documents |
| Cloud Storage | List and download files |
| Firebase (write) | Remote Config, App Distribution, Authentication admin |
Extended access
Some actions need Google’s broader cloud-platform scope — for example listing Cloud Functions, or writing to Firestore and Remote Config. Firedeck does not request this scope at sign-in. The first time you use a feature that needs it, Firedeck asks for it in context, so you grant it with full knowledge of why.
Multiple accounts
Firedeck Pro supports connecting more than one Google account, which is useful if you manage projects across different organizations.