Additional privacy options for recipes on group main page

[mavproductions]

First Check

• I used the GitHub search to find a similar requests and didn't find it.
• Checked the tasks tagged issues and verified my feature is not covered

Please provide a concise description of the problem that would be addressed by this feature.

Right now I'm beginning to setup my Mealie instance for sharing with family members.

I noticed when I log in with a test user that despite my privacy settings for my recipes, they don't work as I expected.

My test user was in a different household, but in the same group.

What I visualize is a whole family line could be in the same group, while being separated by households. To my knowledge households generally have their "secret recipes", or perhaps a few that they like to share with everybody within many households within a group.

For me I have a lot of simple recipes myself that the rest of my family don't need to see, but more so for me to perfect on my own. On the flip-side, I have some recipes that are still rather simple, but the rest of my family would enjoy making themselves.

My hope is that it becomes possible to have some extra granularity for privacy settings within households being within the same group, even if set to public, they can really nail down their own privacy settings for many recipes via current or refined batch permission settings.

Perhaps one of the options is that they have categories/tag(?) labeled something around the lines of "test recipes" which is not shared by anyone but their household, and then they could have another category(or tag?) called perhaps "group shared", which are shared and visible on the main group page.

This allows users to simply batch edit tagged or categorized recipes very quickly where there could have been oversights here under sites of how they wanted their original privacy settings to look like.

Hope this all makes sense, and you consider this as an option!

Please provide a concise description of the feature that would resolve your issue.

See above.

Please consider and list out some caveats or tradeoffs made in your design decision

Not many caveats or trade-offs to my knowledge.

Additional Information

• If this is accepted I'm willing to submit a PR to provide this feature
• If this is accepted I'm willing to help maintain this feature
• I'm willing to sponsor/pay a developer to do this work