HTML Logo by World Wide Web Consortium ( Click to learn more about our commitment to accessibility and standards.

Moving forward with Composr

ocPortal has been relaunched as Composr CMS, which is now in beta. ocPortal 9 will be superseded by Composr 10.

Head over to for our new site, and to our migration roadmap. Existing ocPortal member accounts have been mirrored.

Staff Groups - Designing them right

Login / Search

 [ Join | More ]
 Add topic 
#75116 (In Topic #15587)

Community saint

I am a little perplexed as to which way to proceed on designing my staff groups for one site. I read that you intend to remove the "Staff" system in the future in your tracker somewhere I think so I am curious about what might be good ideas for desiging my groups now that won't cause problems in the future but still give me some flexibility in terms of designating staff?

Like I want to delete super moderator and super member groups and make some new groups. Lets say one of the croups will be called  staff and another group will be called cheif nose pickers and yet another master ear wax cleaners. I can obviously set up permissions the way I want for each group but I want Staff to be listed as staff and hold all the staff of the 2 other groups and nose pickers to me junior admins and ear wax cleaners to be forum moderators but with no access to admin zone. If I leave staff and earwax pixckers
Super moderator
checkmark unchecked then how do I get them in the staff list? I don't want them to have access to the whole admin zone? Sorry if this is in the tutorials somewhere but I couldn't find anywhere that explains it clear enough plus I know you're planning changes which may affect things in the future and proper setup now could make life easier down the road.
Back to the top


You're a little confused, which is understandable.

The staff system and the permissions system are actually different things. Think of the staff system like a list of people the staff module shows.

We want to get rid of it because it's so easy just to create a staff page (or catalogue) manually – so we can remove some bloat and make things less confusing.

To do what you want, forget the word 'staff' and just focus on permissions. I suggest you create a new group choosing to copy permissions from super moderators, but then go and remove access to the admin zone.

Become a fan of ocPortal on Facebook or add me as a friend. Add me on on Twitter.
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about ocPortal whenever you see the opportunity.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying ocPortal on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
1 guests and 0 members have just viewed this: None
Control functions:

Quick reply   Contract

Your name:
Your message: