COmanage Developers List

This is a rough draft, starting the discussion to define the set of 
actions that each of the various roles are allowed. The set of roles 
have been taken from Ken's "rolling deck".

sysadmin
        install a new instance of the software, and configure it

service mgr -- (the person managing a CO instance, which may contain 
multiple COs)
        create a new VO, grant mgmt priv's to others
        archive the content of a VO -- phase 2
        remove a VO definition

collabadmin -- manages a single specific VO
        manage the home page of the CO
	enable a new service to support the work of the VO; use the 
mgmt GUI of the specific application to assign priv's within the 
application
        manage a group (create a group, manage membership, delete the group)
	invite a person to join the VO (automatically adding person 
to some groups)

collabadmin -- manage each service (these actions would be done 
within each service)
	configure a service (eg this email list should be associated 
with ldap group X)
        manage permissions within a service (eg GROUP X can do ACTION Y)

power user -- PI, with some enhanced functionality, a subset


end user
        -- go to the "home page" of the CO
        -- navigate to services supporting the work of the CO
	-- (service specific; uses GUI provided by application) 
various actions within the services supporting the work of the CO, 
depending on how privileges have been assigned