Extend module-admin permission to accept module name suffix

[adrianbj]

Short description of the enhancement

Support permissions like: module-admin-markupseo

Current vs. suggested behavior

Currently you can assign the module-admin permission to a role which gives them access to edit the settings for all modules. I would love to see the option to define module specific permissions so we could limit their access to just certain modules.

Why would the enhancement be useful to users?

There are a few modules out there that I would like clients / site editors to be able to configure, such as the MarkupSEO module, but many modules contain settings that are beyond the skill level of many site editors, and may cause damage to the site. This extra level of access control would be fantastic.

Thanks for considering.

[Toutouwai]

I support this request.

@adrianbj, if you need a short-term workaround for a project, my suggestion in this post might help: https://processwire.com/talk/topic/15510-is-it-possible-to-permit-non-process-modules-configurations-for-non-superusers/?do=findComment&comment=138717

[adrianbj]

Thanks @Toutouwai - I used your example as a starting point and added another hook to limit the modules that are shown in the flyout menus. It's a bit hacky, but it's ok for now.
https://processwire.com/talk/topic/15510-is-it-possible-to-permit-non-process-modules-configurations-for-non-superusers/?do=findComment&comment=163468

[adrianbj]

Hey @ryancramerdesign - any thoughts on this? I am still do the hack noted above, but I really think PW needs this - I know it's something that's possible in Drupal, and I am sure others as well.

Thanks for considering.

PS - if you're not interested in this, it would be great to know, because I might try to build a module that will provide this approach.