[Improvement] Add a per-pool notification mute option

[grantfox-oss]

Getting Started

1. Fork the repository: https://github.com/JointSave-org/Joint_Save
2. Clone your fork:

   git clone https://github.com/<your-username>/Joint_Save.git
   cd Joint_Save

3. Create a new branch:

   git checkout -b feat/per-pool-notification-mute

---

Overview

The existing notification preferences in useUserProfile.ts are global (e.g. "email me on deposit" applies to every pool the user is in). Checked and confirmed there's no way to mute notifications for one specific pool while keeping them on for others — for a user in many pools, this could get noisy if they only care about updates from a couple of them.

Requirements

• Add a muted_pools array (or a join table, whichever fits the existing schema conventions better) to track per-pool mute state per user
• Add a "Mute notifications for this pool" toggle on the group detail page
• Update the notification-sending logic (the Edge Function) to check this mute list before sending, in addition to the existing global preferences
• Muting should be additive with the global preference — both need to allow a notification through for it to actually send

Acceptance Criteria

• Muting a specific pool stops notifications for that pool only, others still come through
• Toggle state persists and is reflected correctly when revisiting the page
• Edge Function correctly respects the per-pool mute alongside existing global preferences

[Ebenezer199914]

can i work on this issue

[phalap1]

Hello I have experience handling technicalities like this, can this be assigned to me.

[WorldsBestSoftwareDeveloper]

I'd like to work on this issue.

I've recently contributed multiple improvements to the Joint_Save codebase through GrantFox, including accessibility enhancements and consistency fixes, so I'm already familiar with the project's structure and conventions.

For this task, I'll implement per pool notification muting in a way that integrates cleanly with the existing user preference system. My approach will be to introduce a per pool mute state that follows the current data model, add a clear toggle on the group detail page, update the notification Edge Function so both global preferences and per pool settings are respected, and ensure the mute state persists correctly across sessions.

I'll keep the implementation focused, consistent with the existing architecture, thoroughly test the notification flow, and submit a clean PR that satisfies all of the acceptance criteria.

[Francis6-git]

I will implement per-pool notification preferences by allowing users to mute notifications for individual pools while preserving their existing global notification settings.

The solution will persist mute state, add a toggle to the group detail page, and update the notification Edge Function to deliver notifications only when both the global preference and the per-pool setting permit them.

ETA 6 hours.

[grantfox-oss]

🦊 GrantFox — @Francis6-git has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #146)
2. Your PR will be reviewed by the JointSave-org maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Francis6-git's PR #167 was approved and merged by @Sendi0011.

🏆 @Francis6-git: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,111 total points). Track your full progress on GrantFox.

👏 Great work, @Francis6-git! Keep contributing to JointSave-org.