[Feature]: Admin Notification System for Collection Rule Modifications

[Touexe]

Is your feature request related to a problem?

Currently, PocketBase provides no visibility when an admin modifies collection rules (e.g., API filters, validation rules). This causes:

• Silent changes: Admins unknowingly work with outdated rules (e.g., "Why did my API endpoint break? Oh, another admin removed the filter yesterday").
• Zero accountability: No way to identify who changed rules or when, making troubleshooting impossible.
• Operational blind spots: Teams can’t track rule evolution (e.g., security policies weakened without review).

Describe the solution you'd like

A passive notification system that alerts admins after rule changes occur:

1. Admin Dashboard Banner:
   • A non-intrusive banner in the admin UI showing:
     "Collection [Name] rules updated by [Admin] • [Time ago] • [View Changes]"
   • Example: "Users rules updated by Jamal• 2h ago • View diff"
2. Dedicated "Rule Changes" Tab:
   • Chronological log of all rule modifications (extending GitHub #2322):
     • Timestamp, admin email, collection name, and before/after rule snapshots.
     • No real-time sync needed, just persistent visibility of historical changes.
3. Opt-in Email Alerts: (My recommendation)
   • Per-admin toggle: "Notify me when ANY collection rule is modified" (or per-collection).
   • Email includes: Admin name, collection, timestamp, and link to diff view.

Describe alternatives you've considered

No response

Additional context

• Why this matters: Rule changes directly impact security (e.g., auth rules) and app stability. Teams need to know when these shift.
• Minimal scope: This doesn’t require conflict resolution. Just recording and surfacing changes.
• Community alignment: Directly addresses gaps in GitHub #2322 (audit logs) by adding actionable visibility.

[AHS12]

I think Pocketbase should be the one to implement this, but we already have a hook set up in this template that can audit every collection change(But not sure it can detect the Rule change), but we are already detecting rule change here for auto API documentation generation, which is costly if you have a lot of collections. I think the most optimal solution would be a cron that runs in the background and collects whether the rule has changed or not. With this and a combination of hooks, maybe there is a solution for the problem you have mentioned.

@Touexe what do you think?