Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I have a need to allow certain users to flag nodes to skip but not change any other Notify settings. Currently the module requires the "administer notify" permission to access the skip flags page, a new "administer notify skip flags" permission would be a nice addition to allow for more finely grained control over what gets sent out.
There is already a separate permission to administer the notify queue, and I think this new permission would compliment that nicely to allow for content administrators to only deal with the content side of things, since those types of users shouldn't be able to administer the entire module settings.
Patch to follow.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | notify-skip_flags_permission-2545996-1.patch | 2.05 KB | jeni_dc |
Comments
Comment #2
jeni_dc commentedHere's a patch that provides a new "administer notify skip flags" permission.
Comment #5
gisleThank you for the patch!
I agree that it should be possible to give certain users permission to administer content notification without having access to the general notofication settings.
However, I do not think it is necessary to create a new and separate permission for this.
The already existing
administer notify queuegives course grained access to the notification queue, with the ability to truncate the queue, etc., and skip flags just adds more fine grained control to this.The latest 7.x-1-x-dev snapshot has been changed to let a role with the permission
administer notify queuealso administer skip flags.If you need to have separate permissions for the course and fine grained administration of the notification queue, I need to know more about the use case.
Comment #6
jeni_dc commentedPart of my use case is to simplify things since I'd rather not have them be able to access the queue page. My users need to be able to flag content to skip and that's all. They're content admins whose only job on the site is to manage the content, they don't have access to anything else. Since they're the ones adding in content, they should be able to choose whether or not a node gets included.
I don't want them to be able to send the emails manually, truncate the queue or override the timestamp. To me those are all administrative tasks which border on configuration and that's where the separate permission comes in.
Having access to the queue page will just confuse them with options they don't need to see, and most likely won't understand even after being informed about what those options do. They simply don't need to change any of those things and therefore shouldn't have the option to access that page at all.
Comment #8
gisleFixed in release 7.x-1.4.