Module Permissions

Events happening in the community are now at Drupal community events on www.drupal.org.
tyjamessmith's picture

So, for module developers out there. Why do you decide to use an existing permission instead of creating one that is custom to your module?

At WGU we have various people who are each over small parts of our site: SEO (meta tags, robots.txt, site maps), optimization, content, etc. In an attempt to not complicate each person's administration pages I try to give them just the permissions that they need. This works great until 25 modules rely on the 'administer site configuration' permission. Really? I just want to grant access to one or two of those modules. Is it really that hard to have another permission?

I understand that there are some benefits to piggie-backing on another permission but some of them are a little overused. Do I now hack your modules just to get a nice administration screen?

Anyone else come up with a better solution? Thanks.

Utah

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week