Junior Admins and Super Moderators

[quasar]

I've been trying to work out a way to do this, but so far come across several blanks.

I want to create a 'junior' group of admins and super mods, that have the functionality of the normal admins and super mods, but restricted as to where on the site they can go (in the case of the junior admin, I want to assign only user only admin functionality).

I've tried creating a duplicate of the admin and the super mod usergroups, but when I've done so the user I assign it to (in the case of admins, assigning special permissions) I get the following when I just try to access through that user:

you do not have permission to access this page. This could be due to one of several reasons:
Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

I've checked, and reverting the user back to a normal registered user allows me the access to the site again through that user.

Is that a bug, or am I missing something?

Secondly, is it possible to do what I want to do through how vBulletin works atm?

I've tried searching the forums, but not come up with an answer so far

[Jake Bunce]

Check the permissions on their usergroup. For example, if this is set to No then they won't be able to access any forum pages:

Admin CP -> Usergroups -> Usergroup Manager -> Edit Usergroup -> Can View Forum

If you continue to have problems then I need to know exactly what page they are unable to view.

_____

You can edit moderator permissions in your:

Admin CP -> Forums & Moderators -> Show All Moderators

You can edit admin permissions in your:

Admin CP -> Usergroups -> Administrator Permissions

[quasar]

I've checked the forum view setting, and it is switched to yes.

The page in question is literally any on the site, including the forum index.

To clarify, I created the new group by 'duplicating' it by using the Create Usergroup Based off of Usergroup: option and picking the admin or super moderator group. I then changed the name only.

I also used the default permissions for the admin and super mod group when creating it.

I hope that helps.

[Jake Bunce]

Submit a trouble ticket with a URL and admin login to your Admin CP and the username of one of the users who can't access the forum:

http://members.vbulletin.com/members...ontactform.php

We will take a look.

[quasar]

I may do Jake, though I think I've figured out what's causing the issue, though why, I'm not sure.

I've been playing around with a different user, and got it to work on theirs account.

When looking into it I noticed the only difference was that the second one I attempted to do it on had an additional usergroup.

So I went back to the first user, added the junior admin role, then the admin permissions, then added a second usergroup. The result was it worked. Removing the additional usergroup, and it goes back to not working.

I do have several hacks installed atm, so I'm gonna run some tests on my backup copy disabling the other hacks to see if they're interfering. Will post back here the results.

I can work around it with the secondary groups, as my intention is for the junior admins to receive additional access through what additional usergroups they are in, so it's not a 'problem' for me, but I would like to know what causes it.

[Jake Bunce]

Additional groups can only add permissions. That sounds like the primary group doesn't have permission in the first place, but the additional group is adding permission.

[quasar]

The additional group in this instance adds access to one forum only, and doesn't have any special permissions like administrative or super mod controls.

[Jake Bunce]

That's something we can check if you submit a trouble ticket.

[quasar]

I've had a look over things again, including disabling the hacks, and realised it was a problem with vbAdvanced permissions that were the problem. With them corrected, the whole thing sorted itself.

I want to say thanks for helping out. I've never found a genuine bug in vBulletin, and I feel you guys do an excellent job