Liam Reilly writes:
Is there a way to have more granular permissions in Postorius than either User or Superuser?
Not without additional code. It couldn't be a plugin. It would have to be a fork of the main Postorius code at first (ie, you would be responsible for patching it and merging our public releases, there would not be regular releases). I doubt it would be merged in a near- future release, at least I wouldn't be confident enough to do that myself without beta testing on a branch.
I don't think it would be hard to implement a "restricted superuser" role. The annoying part would be figuring out where to apply it, as the "authenticated user", "moderator", and "superuser" roles are implemented via Python "decorators" applied to the functions implementing the various features. And the changes would likely need to be pervasive in page templates, forms, and functional code.
The user permissions that are configurable under /admin/auth/user/ do not seem to have any effect.
As far as I know the only bit that has big effects is "superuser", and there's a "staff" bit that has some effect on the superuser IIRC. Everything else is implemented in Postorius.
We have a helpdesk team that would benefit from being able to access all list pages in the same way as a Superuser, but without the ability to accidentally delete the mail domain for example.
I almost started on this two years ago, but that customer wanted it for individual lists rather than a helpdesk team, and realized that all the relevant owners would be satisfied with promoting moderators to owner. So it didn't happen.
Footnotes: [1] There are several consultants who would be capable of maintenance in the consultant list on the wiki, and more than one who would be able to design and implement the code if you're in a we-want-it-enough- to-pay hurry.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan