Re: Admin role
Reply #1 –
Perhaps just more detailed admin permissions would be better than creating grouped roles that some sites will never need. The first thing I usually do as an admin is delete a lot of defaults in a board install, including the Global Mod group. I'd have to do the same with this new admin group.
Splitting and allowing more fine control of admin permissions might be the way to allow admins to create their own "sub-admin" group and allot them the permissions they want, rather than what Elk thinks are necessary.
Re: Admin role
Reply #2 –
You are an experienced user.
Most of the people I have in mind would just put anyone into the admin group, and then regret the fact.
I don't see it as "Elk thinks for you", I see my suggestion more like "hey, you can do that, no need to give away full admin rights".
Of course one can then tune the groups the way he likes.
I think the vast majority of the scripts out there comes with pre-defined stuff just to make it easier for people approaching the script the first time not get lost in a tons of permissions (and you should know the permissions admin panel is not exactly "friendly").
Re: Admin role
Reply #3 –
I know other software( not naming names) has a super admin and only one of then unless you edit the config.php. This super admin has access to everything both in the ACP and server side if needed. You can the have admins but they won't have the access that the super admin would have. Not sure if that helps
Re: Admin role
Reply #8 –
I would hand out soft delete and non admin status removal permissions to 3 rd parties in case of need.