Thank you for your interest and answers.
The problem with static roles defined by architects of NethServer is that this will never fit the need of contributors. I mean you will decide and create categories of users or groups, but what about of exceptions…panels created after your reflexion, or forks of other panels
For example, now I can create really thin permissions, a user can be allowed to use some, all, or just one Panel. Sometime you don’t need to delegate all Panels…or same for a group.
The delegation should be considered also for one User.
What I have in head should be that to templatise /usr/share/nethesis/NethServer/Authorization/base.json with the event nethserver-base-update (could be others also) and contributors could add their own permissions like I did for users and groups.
At the end you could change permissions with db or a panel (I know that you love Panel @giacomo)
-
for group
db accounts setprop adminenmousse AdminPanels Ssh,LogViewer,Group,SharedFolder
or for all panels
db accounts setprop adminenmousse AdminPanels *
-
for user
db accounts setprop plop AdminPanels Ssh,LogViewer,Group,SharedFolder
or for all panels
db accounts setprop plop AdminPanels *
Obviously I have a Panel in Head, I need to search a bit how to do it but in short I want to make an array of all *.php in /usr/share/nethesis/NethServer/Modules and build a SELECTOR_MULTIPLE with checkbox
What I want is to automatise the panel creation for Modules created after this one…perhaps we could templatise the translation file and retrieve Panel name from /usr/share/nethesis/NethServer/Languages
Of course works in nethserver-base could be done by me, under your orders… sirs 
Do I’m dreaming ?