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

[Alex King]

> 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?

Create a 'can_edit_{tax-slug}_content' role or similar.

> 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?  

That's just tooling - if a user only has access to a single section, silently add that term as appropriate to content they create. If they cross over into multiple sections, they then need to select the appropriate sections. This is a training issue.

> 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?

Limit the views of these users in the admin as approprioate

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

See above.

Cheers,
--Alex

http://alexking.org | http://crowdfavorite.com




On Jul 31, 2013, at 11:20 AM, Chris Williams <chris at clwill.com> wrote:

> 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...
> 
> Thanks
> 
> 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.
>> 
>> Cheers,
>> --Alex
>> 
>> 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
>>> possible.
>>> 
>>> 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.
> 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers