No way to add top-level (non-collection) custom Firestore rules in FlutterFlow

[justinmichlewis]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Hi,

Our live Firestore rules include two top-level rules that aren't scoped to any collection:

match /{document=**} {
allow read, write: if request.auth.token.email.matches("firebase@flutterflow.io");
}

match /{document=**} {
allow read, write: if request.auth != null;
}

These were added manually via the Firebase Console and cause a permanent "Out of Date" warning in FlutterFlow, since the rule builder only generates collection-scoped rules. I found the Exclude toggle for per-collection custom conditions, which works well but it doesn't apply to rules that aren't tied to a specific collection.

Is there any way to add rules like these through FlutterFlow, or is manually managing top-level rules outside the tool expected to permanently show as "Out of Date"? Note this occurred after a merging a branch into Main, before there was no warning. And the firestore rules history shows that it was not changed within the last 4 weeks. Appears this might be a bug or a feature gap syncing from FireBase to FlutterFlow for the raw rules code?

Thanks!

Expected Behavior

Ability to sync/reconcile Firebase rules with FlutterFlow. If adding custom rules/logic in Firebase which FlutterFlow's UI doesn't support, an warning message will appear noting the out of date rules. This has the potential for a user to see this and push updates to Firebase rules from FlutterFlow, overwriting the correct rules in Firebase.

Steps to Reproduce

1. Update Firebase>Firestore rules with custom rules within Firebase
2. Create branch off main
3. Modify branch
4. Merge branch back into main

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4giMn1z8pgocMB17rUcu9apCAWG1AiRK00sNobbxAjIoDoPJkUaeDOahRtZ/2gd29DKEWJnmoHwezqhd/XJfQEYEmYRaJayqhQdBXiRnu/aoSXO4eeT3xCO8ZUJ0iY0qurvRZNKtVpV1IN72WyPuvKcA7aQ5/7Zwh9f6PHaOI=

Visual documentation

Environment

- FlutterFlow version: 7.0.65
- Platform: MacOS Desktop
- Browser name and version:Chrome151.0.7922.72
- Operating system and version affected: FlutterFlow desktop and web app

Additional Information

No response

[pstatile]

+1 to this. I have a change in the default behaviour of 'ff_user_push_notifications' and then I can't deploy rules from Flutterflow because if not, it will override my own config that is not a collection.
Hope this is taken someday soon.

[Alezanello]

Hello!

Anything managed outside of FF is considered out of date because FF treats the rules defined within the project as the source of truth.

I'm going to reclassify this as a feature/enhancement request rather than a bug, so this GitHub issue can remain focused on bug reports.