[katello-devel] Fwd: [kalpana-devel] Main Role Use Cases

[Bryan Kearney]

On 05/27/2011 11:05 AM, Todd B Sanders wrote:
> On 05/27/2011 10:57 AM, Todd B Sanders wrote:
>> Moving over to katello-devel.
>>
>> -------- Original Message --------
>> Subject: 	[kalpana-devel] Main Role Use Cases
>> Date: 	Fri, 27 May 2011 10:24:07 -0400
>> From: 	Bryan Kearney <bkearney at redhat.com>
>> Reply-To: 	Kalpana Development Discussions <kalpana-devel at redhat.com>
>> To: 	Kalpana Development Discussions <kalpana-devel at redhat.com>
>>
>>
>>
>> Per a conversation on IRC, here is a first cut of what I think are the
>> main use cases we want to support with Roles. Lets discuss here, and
>> when finalized I will move to the wiki.
>>
>> 1) Users should be granted access to an one Tenant (top level org) but
>> not another. Some users will be read only on the org, others would be
>> able to do stuff.
>
> Help me understand again about the super-admins that have access across
> all tenants? How is this defined?

I would say a super admin has roles on all orgs.

>
>> 2) Around Packages, we want to enable/disable:
>>    A) Creating Providers, Syncing Content.
>
> and uploading custom content.

added

>
>>    B) Seeing products
>>    C) Promoting should be controlled by the environment.
>> 3) Around Environment, we want to protect:
>
> What about CRUD on Environments within an Org, or changing the promotion
> flow?

added.

>
>>    A) Access to the environment.
>>    B) Promoting into the environment.
>> 4) Around Templates:
>>    A) Creating / Editing Them.
>>    B) Promoting should be controlled by the environment.
>> 5) Around Systems, we want to protect:
>>    A) CRUD basd on the environment they are in.
>>    B) Remote Command and Control
>
> System Groups?
>

Added.

-- bk