As of uPortal 3.1, channel management may be delegated to particular groups of users, such that management permissions can be scoped to particular categories. It seems like that feature would interact nicely with the new lifecycle management that will be available in 3.2 ( http://www.ja-sig.org/wiki/display/UPC/Portlet+Lifecycle). This work is currently entered in JIRA as http://www.ja-sig.org/issues/browse/UP-2501.
I'd like some feedback on how we'd like the permissions for this new feature to work. The simplest solution might be to add a new management permission for each lifecycle step, and let each new permission represent the ability to manage or promote to a particular lifecycle step. For example, MANAGE_APPROVED might represent the ability to approve a channel or to make changes to approved channels. I don't know if we might also want to consider assuming that having a permission for a particular lifecycle step also implies permission for all previous lifecycle steps. For example, maybe we want to assume that anyone that can publish a channel can also approve one. That would ensure that administrators with permissions to publish a channel could also unpublish the channel. If we needed to, we could of course split permissions out even further, such that the ability to promote channels to a particular lifecycle state and the ability to edit them once in that state is separate. Unless we really need this, this might be more complication and confusion than it's worth. What kind of permissions structure would everyone like to see? - Jen -- Jen Bourey -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
