[development] Even more flexibility in content management

[Earnie Boyd]

On 12/28/06, Rob Barreca <rob at electronicinsight.com> wrote:
>  A bit off-topic and not super critical, but this will also need to spur a
> discussion of a more manageable access control page if we have something
> like 5 perms for each content type. Is there an issue/any ideas on how to
> simplify the access control page? Or, is a super long matrix format still
> the best way to go?
>

Let's think it through a bit:

Read, Create, Delete (RCD)
Self, Group, Others   (SGO)
Host, Module, Content (HMC)
Admin, Non-Admin (AN)

Does this cover the access control groupings we need?  I.E. Did I miss 
anything?

* User with RCDA rights at Host controls all.
* User with RCA rights at Host controls all but may not delete or disable.
* User with RCDN rights at Host and RCDA rights at Module (each module 
is specified) would be able to read, change and delete all content, 
would not be able to admin (publish or promote) content unless that 
content was with the RCDA module list.  This user also has the ability 
to modify the settings that control the Module.
* ...

So how do we apply this to the role we are creating?  The view of the 
role form would need to change so that above groupings become a 
checkbox group and the form would have a module list box.  The user 
creating the role would check the values wanted and then select the 
modules it applys to.  The list of modules would include selection for 
<all> modules and would be the default.

Earnie Boyd