Skip to main content

So last Sunday, I briefly checked our community queue (like any CM with no self-control would do) and saw that our CEO had replied to a customer. We always have pre-mod on during holidays and weekends and I had a minor freak out worrying he’d be frustrated his post got caught in the approval process. He was fine with it, but it reminded me I need to figure out how to let employees bypass pre-mod.

I think the most obvious solution is to add all employees to the Superuser role as we’re not using it otherwise, but is there a better way?

Also, at some point over the past year someone on my team apparently deleted the Superuser role from the role list. I’ve added it back by just recreating a Superuser role, but is that enough or was there more behind the scenes?

Thanks!

Hi ​@jillian.bejtlich !  :) I think that indeed the best solution is to give your employees one of the primary roles that sidesteps the pre-moderation filter: Administrator, Community Manager, Moderator or Super User.  I can’t think of an easier way.

Note that it’s the primary role called ‘Super User’ that you need to select in this case.  It’s not possible for anyone to delete a primary role.  I had a quick peek in your community and I can see that you have a Super User primary role (that’s there in all of our communities) and a Superuser custom role.  It’s possible that someone deleted your custom role at some point.

Hi ​@Kenneth R - Thanks for the reply and checking our community too. Looks like our custom role was what kept getting mucked around with.

I feel like I’m having a moment over here (of forgetfulness): Is there any easy or automated way to apply the Super User primary role to multiple users at once and/or moving forward?

Hey ​@jillian.bejtlich - I can’t think of an easy or automated way to apply primary roles at scale, unfortunately.  In most communities, the majority of members are ‘Registered Users’ and the volume of Admins, CMs, Mods and Super Users is usually fairly low.  I expect that’s why we never had a strong use case for including primary roles as a bulk action.  

Terms & ConditionsCookie settingsAccessibility statement