Campaigns "Security"

[PeteKersker]

First of all, Listmonk is an excellent product. Thank you for all you have done here!

I'm working to implement the newest version (4.1.0) in my multi-user environment. I'm utilizing OIDC SSO with Nextcloud as the OIDC provider. It works perfectly! I'm also trying to set up security for each user (bloggers, etc.) so they do not stomp on each other. I'm able to accomplish this quite well with:

• Subscribers - using User Roles: subscribers_get (and turning off subscribers_get_all)
• Lists - using List Roles: View & Manage the list(s) I set up for them.
• Campaigns - I have not found a way to filter the list of campaigns.

Is your feature request related to a problem? Please describe.
Is there a way to filter the list of campaigns a User can see based on other security set in place? I'm trying to keep the users from accidentally deleting another User's campaign. I know the User/Security/OIDC parts are new and the documentation is still catching up. So, I figured I'd start with the question.

Describe the solution you'd like
If this is not currently possible (limiting campaigns on the list), perhaps a "campaigns_get_all" security level could be added to the User Roles. This role could show all campaigns the way it works currently for "campaigns_get". This would free up "campaigns_get" for a more limited, user-specific list. Perhaps the list could be limited by campaigns connected to lists the person has security to view and/or manage? Just thinking out loud here.

Thanks again for your great work. I'll look forward to your thoughts.

[knadh]

Hi @PeteKersker. This isn't supported currently and the solution you had proposed is what I had in mind originally. However, I recollect running into some gotchas while trying to implement it. We can consider this for a future version.

[PeteKersker]

Ok. Thank you for letting me know so quickly. I'll move forward on my end and work through it with training and documentation for now. I'll keep watching to see when you're able to work through those glitches. Let me know if there's some way I can help. Thanks again!

…

On Tue, Feb 25, 2025, 11:30 PM Kailash Nadh ***@***.***> wrote: Hi @PeteKersker <https://github.com/PeteKersker>. This isn't supported currently and the solution you had proposed is what I had in mind originally. However, I recollect running into some gotchas while trying to implement it. We can consider this for a future version. — Reply to this email directly, view it on GitHub <#2325 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD4SSGOKSPVZOTSO2ZZUXMT2RVGOLAVCNFSM6AAAAABXZDHBR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBTHEZTQMBXHE> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: knadh]*knadh* left a comment (knadh/listmonk#2325) <#2325 (comment)> Hi @PeteKersker <https://github.com/PeteKersker>. This isn't supported currently and the solution you had proposed is what I had in mind originally. However, I recollect running into some gotchas while trying to implement it. We can consider this for a future version. — Reply to this email directly, view it on GitHub <#2325 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD4SSGOKSPVZOTSO2ZZUXMT2RVGOLAVCNFSM6AAAAABXZDHBR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBTHEZTQMBXHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>