Having used vB and IPB in the past, I'm finding the new permission system in XF a royal pain in the back side. For instance, if I assign someone to the Admin usergroup, I would expect them to be able to not only have all Admin privileges, but all moderator privileges as well. I'm finding I have to assign an Admin to BOTH usergroups in order for them to see all the moderation tools in the forums.
Not all staff/admins require moderation permissions it's quite frankly permission implementation i think was superbly done by the developers. You are able to assign moderation privileges to that specific admin if you require there's nothing stopping you from applying and setting up that admin to use the moderating tools. There was a debate about this at xenforo and I have to agree each admin has there own set of duties and tasks which calls for those specific permissions.
You don't have to assign them to an admin and moderator usergroup, but you do have to add them as admins and moderators. Sounds more confusing than it is. Quick tutorial:- In your ACP, go to Users and select Administrators. On the new page, click Create New Admin, type in the User's name, put him in the admin group and then select which admin permissions you want him to have. To give the same user mod abilities, go back to Users, and this time select Moderators. Create New Moderator, don't bother adding them to the moderating usergroup, and select the abilities you want. That keeps them in your Admin usergroup, but with Moderator abilities.
However, one would think that assigning a person to the Admin group would give ALL site rights. You can then go in and hand massage any specific rights you don't want the individual to have. I'm old school. When you give someone "admin", they typically have rights to everything. Apparently this isn't the case with XF which is driving me nuts. >.<
heh heh heh I feel your pain. I struggled for a while too. But it's actually beautiful in its simplicity. You can have admins for specific things, moderators for specific things, admins who are mods, admins who aren't mods... all without having to touch the usergroups.
Permission issues aside (I still think it's a messed up system), I'm finding it a joy to work with. The ability to modify certain aspects of the default style is light years ahead of everyone else.
I'm old school too, but I've come to enjoy the new system. I have found uses for it, for example, my "site manager" has admin rights to certain things but is mostly a moderator. He's basically a super-super-mod with a few admin rights that are required to do some of his duties. Its a little more work up front to set up this way, but it makes the system more flexible for sure. To me its kinda like my Linux desktop user accounts. There is a "root" user that I hardly ever have to log-in as, there is my account with the ability to use the sudo command when I need root privileges, and there is an account for guests that is pretty much restricted to just web browsing.
Yeah, but when you assign root (Admin) you have the keys to the kingdom. I can see why they did it the way they did. I just disagree on the method it was implemented. Seems a bit bass ackwards to me.
Eh, there are strong arguments for both ways of doing this. Permissions have always been one of those things that never seem *just right* and can quickly become a nightmare.
NetWare did it perfectly. Admins had all privileges. IF you needed to modify, you allowed inheritance to flow downwards and then restricted permissions at the exact level you needed to modify permissions. Inheritance then flowed down from that point. Same with users. You assigned permissions at the organizational level and allowed inheritance to flow downward from there. You then had the ability to modify at lower levels as needed. Software designers rarely know the first thing about administration in an enterprise environment. They get these so called great ideas which make it a nightmare for those who actually have to implement and use it. Assigning permissions should never be something that is a headache. And it should be done from just one location, not multiple locations.
