1222 results found

1. Native support for RBAC (Role-Based Access Control)

   Native RBAC (Role-Based Access Control) management
   Currently, to manage roles (admin, editor, client), you have to use Custom Claims via the Admin SDK (Node.js) or store the roles in Firestore. This is cumbersome for a beginner.

   The improvement: Being able to define roles directly from the Firebase console and have them automatically appear in the request.auth object of Security Rules without additional code.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. let developer enforce schema if wanted on the serverside

   provide an option for the developer enforce a schema in the firebase console. At least on the firestore enterprise edition. Mongo Atlas had this offering. rightnow, we are having to manage schema at the app level and then again at the cloudfunctions level. Making it hard to manage.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firestore  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Improve Firebase Auth integration with Server side rendering (Next.js)

   Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.

   I hope Firebase will consider my feedback.

   Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.

   I hope Firebase will consider my… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Narottam
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Distribution  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Integrate PSEUDOINFERENCING INTO THE COMMAND PROMPT INTERFACE FOR “GEMINI” integration and system management

   Doing TLD SPOFING FOR WEB2:WEB3 TUNNEL MANAGEMENT

   TO ADD EXPLICIT RESTRICTIONS FOR “{TRAP HANDLER}” Inference Modeling

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Cloud Messaging  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Missing Primitives: Transaction Awareness and Trusted Server Metadata in Security Rules

   Firestore Security Rules currently lack two capabilities that force developers to choose between security, performance, and maintainability.

   1. Lack of Transaction/Batch Awareness Rules cannot verify if a write is part of an atomic batch or transaction. This makes it impossible to enforce multi-document integrity constraints natively.

   The Fallout: Developers must either trust the client to perform all parts of an operation (unsafe) or move logic to Cloud Functions. This introduces latency and cold-starts, but more importantly, it fragments security logic. Concise, native rules bolster security because they are easier to audit and are implemented correctly more often than fragmented, multi-layered workarounds.

   1. No "Middle Ground" for Server-Side Operations Currently, a server must either use the Admin SDK (which results in a full administrative bypass of all rules) or Identity Platform to impersonate a user. There is no way for a server to provide "partial validation" for a request that must still remain failable if it violates standard Rule constraints.

   The Fallout: Current limitations incentivize the use of "shared secrets"—checking for specific plain text properties or "magic strings" within the document data to signal that a server has "blessed" the write. This pattern may be adopted because it is more efficient than the alternatives, but it is brittle and mimics security without the actual structural protection of the Rules engine.

   Use Case Examples
   Relational Integrity (The "Escrow" Logic): A Purchase document must be created if and only if the Product status is simultaneously updated to sold in the same atomic transaction.

   External Validation (The "Verified Invite"): A server validates a one-time invite code against a 3rd-party API and "stamps" the request as valid. The Rules then check this stamp alongside request.auth to ensure the user isn't on a blacklist. The server validates the code; the Rules validate the user.

   State Synchronization (The "Booking Lock"): A user booking a hotel room must create a Booking doc and update the Room availability timestamp in one batch. Without is_transaction, rules cannot prevent "orphaned" bookings.

   Requested Features
   request.is_transaction: A boolean allowing rules to reject non-atomic "partial" updates to sensitive multi-document states.

   request.auth.token.server_assertions: A way for the Admin SDK to attach non-forgeable, temporary metadata to a user-authed request. This allows the server to act as a co-validator without needing a full administrative bypass.

   Appendix: Proposed Rule Syntax Examples
   A. Multi-Document Invariants

   JavaScript
   // Ensure a product status isn't flipped without a corresponding purchase record
   match /products/{productId} {
   allow update: if request.resource.data.status == 'sold'
   && request.istransaction == true
   && existsAfter(/databases/$(database)/documents/purchases/$(request.auth.uid)$(productId));
   }
   B. Co-Validation (Failable Requests)

   JavaScript
   // Server verifies the invite, Rules verify the user identity and blacklist status
   match /workspaces/{workspaceId}/members/{memberId} {
   allow create: if request.auth.uid == memberId
   && request.auth.token.serverassertions.inviteverified == true
   && !get(/databases/$(database)/documents/blacklist/$(memberId)).exists();
   }
   Summary: Firestore needs a way to combine user auth with trusted server assertions and transaction visibility. Without these, secure patterns are significantly harder to implement than unsafe ones.

   Firestore Security Rules currently lack two capabilities that force developers to choose between security, performance, and maintainability.

   1. Lack of Transaction/Batch Awareness Rules cannot verify if a write is part of an atomic batch or transaction. This makes it impossible to enforce multi-document integrity constraints natively.

   The Fallout: Developers must either trust the client to perform all parts of an operation (unsafe) or move logic to Cloud Functions. This introduces latency and cold-starts, but more importantly, it fragments security logic. Concise, native rules bolster security because they are easier to audit and are implemented correctly more often than fragmented, multi-layered workarounds.

   1. … more
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firestore  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Gemini in firebase

   I think it would be a great idea to be able to create more one context chat with gemini , with ability to link them together , or merging them.

   Especially while gemini right now in Firebase , is very It is very distracted and does not adhere to instructions and commands and performs actions repeatedly and repeatedly outside the user's control, also it should be made more committed to the instructions and it has not been clearly indicated previously not to do so, for example if you ask to change the color of a button on the site, you will be surprised that it has made several other changes such as changing the size of the button or deleting the text above it.

   I think it would be a great idea to be able to create more one context chat with gemini , with ability to link them together , or merging them.

   Especially while gemini right now in Firebase , is very It is very distracted and does not adhere to instructions and commands and performs actions repeatedly and repeatedly outside the user's control, also it should be made more committed to the instructions and it has not been clearly indicated previously not to do so, for example if you ask to change the color of a button on the site, you… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Gemini in Firebase  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Allow users to easily leave or disconnect from Firebase projects they no longer belong to

   When developers change companies or stop collaborating on a project, they often remain listed as members of Firebase projects that they no longer use or have access to.

   Currently, the only way to be removed from a project is for a project owner or administrator to manually remove the user from the project permissions. This becomes problematic when:

   The developer no longer has contact with the project owner

   The company forgets to remove former collaborators

   The user wants to clean up their Firebase project list

   I suggest adding a “Leave Project” or “Disconnect from Project” option directly in the Firebase console for members.

   This feature could:

   Allow users to remove themselves from projects they no longer work on

   Improve security by reducing unnecessary access to company resources

   Help developers keep their Firebase console organized

   Reduce administrative overhead for project owners

   For example, developers who change jobs often still see old company projects in their Firebase dashboard, even though they no longer use them.

   A simple self-removal option would solve this problem in a secure and user-friendly way.

   When developers change companies or stop collaborating on a project, they often remain listed as members of Firebase projects that they no longer use or have access to.

   Currently, the only way to be removed from a project is for a project owner or administrator to manually remove the user from the project permissions. This becomes problematic when:

   The developer no longer has contact with the project owner

   The company forgets to remove former collaborators

   The user wants to clean up their Firebase project list

   I suggest adding a “Leave Project” or “Disconnect from Project” option directly in the Firebase… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. preview env links support

   currently its needed to deploy the app to firebase hosting AND firebase app hosting to get preview links working, thats making things more complex than needed...

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Job development

    Animated script for game development video prompts analytics workspace for project management

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Agent Skills  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. سهل الربط بالتسلسل بين خدمات غوغل كلاود وطرق الدفع واستقبال الدفعات تحت شاشة مراقبة ضمن صفحة المؤسسة لدى العميل على غوغل وورك سباس

    سهل الربط بالتسلسل بين خدمات غوغل كلاود وطرق الدفع واستقبال الدفعات تحت شاشة مراقبة ضمن صفحة المؤسسة لدى العميل على غوغل وورك سباس

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Agent Skills  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. I want to able to set Cloud Run Execution Environment in Cloud Functions

    https://docs.cloud.google.com/run/docs/configuring/execution-environments

    Since Cloud Functions v2 run on Cloud Run and Cloud Run supports two different execution environment, I want to be able to set them, e.g.

    const { onRequest } = require("firebase-functions/v2/https");

    // Set it for a specific function
    exports.myFunction = onRequest({
    executionEnvironment: 'gen1', // This tells Cloud Run to use its Gen1 environment
    memory: '256MiB',
    }, (req, res) => {
    res.send("Running on Cloud Run Gen1 environment!");
    });

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Cloud Functions for Firebase  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. GGV Hub: A Physical AI Ecosystem integration with Firebase and Gemini for Autonomous Retail

    Proposal: GGV (Google Gemini Valley) Hub
    I suggest integrating Firebase with Gemini to power a physical AI-driven ecosystem called "GGV". This concept features:
    Full-Auto Retail: A Gemini-managed supermarket with robotic assistance.
    AI Cinema: Dynamic content generated in real-time by Google’s AI models.
    Smart Workspace: High-tech, acoustic-insulated office pods for rent.
    This physical landmark will serve as a "Soft Power" asset for Google, showcasing Gemini's real-world dominance beyond digital interfaces

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Agent Skills  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Request to make "flutter deploy" to allow Incremental Remote Config parameters update

    Take this case,

    An Enterprise Project with multiple Mobile Apps underneath. In our case, it is an ERP system with multiple subject-based mobile apps. Each mobile app needs to control its forced-update on the client side. Remote Config is thought to be the way forward.

    We need to have "flutter deploy" update a parameter for each app, to keep the latest version. The app will check this against its bulit-in version number. If a mismatch, then force an update. Very typical scenario.

    The issue with the current "flutter deploy" as a method to automatically update/maintain Remote Config parameter for the App, is that is erases all other parameters for all other apps in the same project !!

    A remote config file such as
    {
    "parameters": {
    "myapplatestversion": {
    "defaultValue": {
    "value": "A2001-AI0109"
    },
    "valueType": "STRING"
    }
    }
    }

    is missing a directive, to state if this is a New (Add) or Update, or Overwrite the entire project partameters.

    Currently, the firebase Console allows this sort of incremental maintenance of the project parameters. Therefore, it is only normal to expect the Deploy API to provide the same functionality of the portal.

    We are willing to help, if you need an extra hand to program the feature !

    Take this case,

    An Enterprise Project with multiple Mobile Apps underneath. In our case, it is an ERP system with multiple subject-based mobile apps. Each mobile app needs to control its forced-update on the client side. Remote Config is thought to be the way forward.

    We need to have "flutter deploy" update a parameter for each app, to keep the latest version. The app will check this against its bulit-in version number. If a mismatch, then force an update. Very typical scenario.

    The issue with the current "flutter deploy" as a method to automatically update/maintain Remote Config parameter for the… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. 1251 end

    VIP NUMBER

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. RobLO
    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. ระบบตรวจบัตร (Auth): สร้างหน้าจอ Login สี #1A7AE6 ที่มีความปลอดภัยสูงสุดสำหรับท่าน?
    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Test Lab  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Review the Ai Coding Output

    Review the code output of the built in Ai and Gemini 3.0 flash preview , i have recently created multiple new projects and then instructed gemini to produce my ideas and 9x/10 the app is somewhat built and with many errors and mistakes in the firebase code the app will only make it to a certin point and then suddenely it is destoryed forcing the ai to try to recover the damage it has no idea what its trying to fix and then instead of working on your own project your ai is trying to rebuild the firebase app infrastructure just to run correctly.. this is extremely frustrating but somewhat understanding currently as the firebase studio is still in preview development. also from this i feel the ai isnt designing real apps it is mostly building a simulation app that is not ready for production without a real human paid developer to take over and finalise as a home user this is very frustrating also... #betafeedback. #ijustwanttotry&buildarealworkingappnow!

    Review the code output of the built in Ai and Gemini 3.0 flash preview , i have recently created multiple new projects and then instructed gemini to produce my ideas and 9x/10 the app is somewhat built and with many errors and mistakes in the firebase code the app will only make it to a certin point and then suddenely it is destoryed forcing the ai to try to recover the damage it has no idea what its trying to fix and then instead of working on your own project your ai is trying to rebuild the firebase app infrastructure… more

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    7 comments  ·  Gemini in Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Perform automatic rollouts only for changes to configured app directory

    I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

    Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a common feature in CI/CD and I'm surprised to find that this isn't the default behavior. We should be able to specify which path(s) App Hosting monitors for changes, so that it doesn't needlessly roll out every time I make a change in the monorepo that doesn't affect the app.

    I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

    Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. A native feature that allows developers to easily export all data related to a specific user from their Firebase project.

    The idea is to add a native feature that allows developers to easily export all data related to a specific user from their Firebase project. Many applications must comply with privacy regulations that require them to provide users with a copy of their personal data. Today, developers usually need to build custom scripts to search across multiple Firebase services, which can be complex and time-consuming.

    The proposed feature could be called User Data Export API. With a simple backend request using a user UID, Firebase would automatically scan all relevant services in the project and collect the data associated with that user. This could include documents stored in Firestore, files in Cloud Storage, authentication data such as email and account metadata, user preferences, messages, and other application data linked to that UID.

    Firebase would then generate a structured export package, for example in JSON format along with related files. This package could be downloaded directly from the Firebase console or accessed through an API endpoint, making it easy for developers to deliver the data to users when requested.

    An additional improvement would be optional integration with Gemini. Once the raw data export is generated, Gemini could automatically produce a human-readable document summarizing the user’s data. Instead of sending a large and difficult JSON file, the system could generate a clear report explaining what information is stored, such as account details, activity history, uploaded content, stored files, and user settings.

    Firebase could also include a dashboard in the console where developers can trigger an export for a specific user, monitor export history, and download the generated reports.

    This feature would significantly simplify compliance with privacy regulations such as the GDPR and the CCPA, while saving developers a large amount of engineering work. By integrating this capability directly into Firebase, data exports would also be more consistent and reliable across all Firebase services used by an application.

    The idea is to add a native feature that allows developers to easily export all data related to a specific user from their Firebase project. Many applications must comply with privacy regulations that require them to provide users with a copy of their personal data. Today, developers usually need to build custom scripts to search across multiple Firebase services, which can be complex and time-consuming.

    The proposed feature could be called User Data Export API. With a simple backend request using a user UID, Firebase would automatically scan all relevant services in the project and collect the data associated with… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating