Closed (fixed)
Project:
Mass Contact
Version:
5.x-2.4
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Jun 2008 at 01:38 UTC
Updated:
12 Aug 2008 at 22:53 UTC
It would be nice to be able to restrict who can send to the various categories. In my case, I have a group of kids and adults, the kids are part of small groups that make up a larger organization.
We don't want everyone to be able to send to everyone. So we want a "can send to adults" or "can send to kids" or "can send to group A and B of kids, but not group c".
If this is too much, then the ability to restrict sending to a role to people who are in that role would be a good second best option for us.
Comments
Comment #1
csilver commentedLet me clarify... (using a different account, but I'm the person who submitted the question)
When using the mass contact form to send the email, there is a list of categories to select for who should receive the email. I'd like to be able to restrict this selection based on the role(s) associated with my account.
Comment #2
oadaeh commentedMaybe Organic Groups is really what you want.
I'm not sure that creating permissions based on arbitrary settings is feasible in Drupal.
Since the categories are based on one or more roles, and the categories are what is presented to the user at form time (not the role(s) those categories represent), it'll be a little more challenging to do that.
However, I don't think it's impossible, but I don't see myself doing that any time soon. In actuality, I would possibly consider this more of a feature for a plug-in, which I do see myself doing in the future.
Comment #3
oadaeh commentedAfter rethinking this, it occurred to me that I could implement this similarly to how content type permissions are implemented. So, of course, changing category names will delete previously set permissions, but that is what people have to deal with when changing content types, as well.
This has been done for HEAD, DRUPAL-6--1 and DRUPAL-5--2.
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.