I have been trying to figure out a way to manipulate the permissions so as to allow members of a certain role the ability to create newsletters... but then when creating a newsletter issue... only be able to send that issue to the newsletters that they have created, instead of any newsletter on the site that has been created by anyone. I use the "newsletter issue" as the content type for an issue if that matters at all. Can this be done? Thanks!

Comments

nally’s picture

nally commented

I would love to see this fine grained permission also. I was just looking for it today.

nally’s picture

nally commented

Since the individual newsletters seem to be taxonomy terms, could it be that http://drupal.org/project/taxonomy_access would help here?

nally’s picture

nally commented

I've had initial success with this. I create a role that can create simplenews content. Then, for that role, I create a taxonomy access configuration that by default denies access to all other terms in the vocabulary, and then permits access to the individual newsletter I'm allowing that role to create.

This looks like a fairly complex process, and I hope I haven't screwed up my other taxonomy stuff in the process. :-) We'll see.

Bigpappaj’s picture

Bigpappaj commented

Thanks for the replys... the only problem with all of that is I would like to allow people to actualy create the newsletters... not just the issues to be sent out. So they would be naming them whatever they wanted them to be named for what they were doing.

sutharsan’s picture

sutharsan commented
Version: 6.x-1.0-rc6 » 6.x-2.x-dev
Category: task » feature
simon georges’s picture

simon georges commented

I think it's just a taxonomy access problem, as nally was suggesting. This should probably be addressed by a contrib module instead of Simplenews "core".

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented
Version: 6.x-2.x-dev » 7.x-1.x-dev

Right. in 6.x-2.x and simplenews core such a feature won't exist.
You might use taxonomy access -- but note there are some notes about incompatibility...

For D7 i can imagine new enterprise features to manage more scalability and permission granularity...

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Related to #1140606: Permissions Per-Newsletter: Limit subscription options by role, but different.

Also, as mentioned there, taxonomy access doesn't work for this. You can't differentiate between the ability to subscribe to a newsletter and sending issues of that newsletter. The node/term access system works by altering queries, you are missing the context for when you need to allow and when to deny access.

If I understand this correctly, you are trying to allow users to set up personal newsletters on which other users can then subscribe to. I'm actually not sure what's the best way to accomplish something like this with our current architecture.