[wp-hackers] Managing a lot of content editors, roles and permissions

Chris Williams chris at clwill.com
Wed Jul 31 17:20:13 UTC 2013

Alex, I'm facing a similar conundrum (or should I say fiefdom...).  Can
you elaborate?  

You create a taxonomy for each division/department: abc.com/sales,
abc.com/development, etc.  And for that each of those you create a set of
author/editor/publisher/admin roles?  Is that right?

Each author is responsible for choosing the correct taxonomy for their new
content?  What if they choose incorrectly?  Do they see the entire
taxonomy, or just their window?  E.G., if I'm an author in Sales, do I see
all the departments in the Edit Post page?  Or just Sales?  Or does it
somehow just put my post in Sales?

Does this prevent an editor from division A from creating/editing content
in division B's taxonomy?  I assume so...


On 7/31/13 9:15 AM, "Alex King" <lists at alexking.org> wrote:

>Our experience has been that siloing content via WPMS is more problematic
>long term that building custom permissions. We have used custom
>taxonomies plus matching custom roles to address this nicely on several
>large scale sites.
>http://alexking.org | http://crowdfavorite.com
>On Jul 31, 2013, at 7:01 AM, Dino Termini <dino at duechiacchiere.it> wrote:
>> Hello list,
>> I am working on a large scale website which has multiple sections
>>(roughly associated to departments in the organization), and each
>>section has its own group of contributors, editors, publishers and
>>administrators. We will be using WordPress MU to segment content editors
>>and assign appropriate roles and privileges to each of them. The site
>>has currently about 80 editors.
>> We've also looked at plugins that extend WP's roles and capabilities,
>>but we would prefer using as much off-the-shelf functionality as
>> I was wondering if the list has any pointers to share about best
>>practices, do's and dont's, etc, on setting up a permission management
>>layer in WP for large scale websites.
>> Thank you,
>> Dino.

More information about the wp-hackers mailing list