...
- Academics
- Administration
- Demonstration
- Development
- Entertainment
- Information
- Instructors
- News
- Testing
- uPortal
Portlet Permissions
Publishing Workflow Permissions
uPortal 3.2 introduced new portlet publishing workflow features that allow a portlet to be moved through the following lifecycle stages:
- Created
- Approved
- Published
- Expired
a series of lifecycle stages. Portlet management permissions for each lifecycle step may be delegated to a particular user or group upon any given portlet category. Upgrading institutions may wish to assign these permissions to administrative groups or users.
Publishing permissions in uPortal 3.2 are as follows:
Workflow step | uPortal Permission |
|---|---|
Created | MANAGE_CREATED |
Approved | MANAGE_APPROVED |
Published | MANAGE |
Expired | MANAGE_EXPIRED |
New subscription permissions were similarly created to allow administrators and developers to subscribe to un-published content.
Workflow step | uPortal Permission |
|---|---|
Created | SUBSCRIBE_CREATED |
Approved | SUBSCRIBE_APPROVED |
Published | SUBSCRIBE |
Expired | SUBSCRIBE_EXPIRED |
Targeting categories and portlets
As of uPortal 3.2, the . regex-based syntax for targeting all portlets was dropped in favor of the static string "ALL_CHANNELS".
The uPortal permissions implementation was also modified to allow inheritence of permissions by targets. For example, setting a permission on the target "Everyone" group will now cause that permission to cascade down to all members of the "Everyone" group. Prior to uPortal 3.2, permissions inheritence was calculated for principals, but not for targets.