1208 results found

1. firestore pipeline as rulev3/transformation

   Additional to just a condition for allow read/write. I think firestore rule should be replaced with transform function. It should utilize pipeline operation and return document to read/write. So that it could force add field or change logic to generate some field on every document without redeploy client

   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  ·  Firestore  ·  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. 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

3. 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

4. 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

5. Support Multiple Data Connect Services in Emulator Suite (or Allow Hybrid Cloud Fallback)

   Currently, the Firebase Emulator Suite allows running only a single Data Connect service instance locally. For projects utilizing a microservices architecture with multiple isolated Data Connect services, this creates a significant blocking issue during development.

   Primary Feature Request: Multi-Service Emulation - Please update the Emulator Suite to support running multiple Data Connect services simultaneously.

   Alternative / Interim Solution: Hybrid Cloud Fallback - If full multi-service emulation is technically complex to implement immediately, please introduce a "Hybrid" mode as an alternative.

   Current Behavior: When the emulator is running, all calls to Data Connect are forced to look locally. If a specific service isn't emulated, the call fails, even if a live version exists.

   Proposed Behavior: Allow an opt-in flag (e.g., --allow-cloud-fallback) that permits the SDK to connect to live/deployed Cloud instances for any Data Connect service not currently running in the emulator.

   Why this is critical: Support has confirmed the current "walled garden" approach is intended to prevent accidental costs. However, without multi-service support, this leaves developers in a deadlock: we cannot emulate our full stack locally, and we cannot mix local emulation with cloud resources. We are effectively forced to test entirely in production.

   Currently, the Firebase Emulator Suite allows running only a single Data Connect service instance locally. For projects utilizing a microservices architecture with multiple isolated Data Connect services, this creates a significant blocking issue during development.

   Primary Feature Request: Multi-Service Emulation - Please update the Emulator Suite to support running multiple Data Connect services simultaneously.

   Alternative / Interim Solution: Hybrid Cloud Fallback - If full multi-service emulation is technically complex to implement immediately, please introduce a "Hybrid" mode as an alternative.

   Current Behavior: When the emulator is running, all calls to Data Connect are forced to look locally. If a specific… more

   3 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  ·  SQL Connect (Data Connect)  ·  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. 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

7. Realtime database, change default tab order

   Reorder the tabs in Realtime DB to prioritize displaying the rules or a landing page before the data.

   New users and analytics management find that loading the Realtime Database section from the web console impacts bandwidth usage for reads. This behavior is not ideal and could be separated from the Realtime Database landing page, especially when editing or inspecting the rules, as it requires loading larger chunks of the database before the user switches tabs.

   13 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

   5 comments  ·  Other  ·  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. Voice over

   I can give my voice over to control

   3 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  ·  Other  ·  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. 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

10. About entertainment
    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  ·  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

11. 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

12. Hi Firebase , I need urgent help with Case 10386349. My Firebase project was incorrectly flagged, and my entire Realtime Database is inacces

    Please check

    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

    2 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

13. 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

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

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

    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  ·  Agent Skills  ·  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

15. Figure out a way to make menus/options User Friendly - I tried setting up Email Trigger in an APP - maybe I will get it figured out a year f

    Fix the menu process flow for set-up - think like a user instead of a Nerd Progrmmer or enable Gemini to do some work for users

    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  ·  Extensions  ·  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. 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

17. Make prototyping AI ask to make changes

    The prototyping AI will automatically start making changes after I ask a simple question. I have to type "don't make changes" after each prompt. It needs to confirm changes before editing.

    7 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  ·  Other  ·  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. Firestore Rules Tab - Separation of Concerns

    Firestore rules tab should allow deploying multiple tabs so that all rules are not in the same rules container in the UI. This will allow us to create separation of concerns(collections) to their own tabs. To prevent massive running list of rules.

    As an example:

    I have 2 collections

    Users
    Pets

    I should be able to write my rules for Users in a tab.
    Then in a completely separate tab, write the rules for Pets

    Then deploy them individually or all at the same time.

    5 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  ·  Firestore  ·  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. meraestore

    Aap store Play store Google service Google product

    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  ·  Analytics  ·  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. BUILD

    LOVE

    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  ·  Authentication  ·  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