On 08/17/2010 01:01 PM, Arlo White wrote: > Though this feature might save a little time you can still achieve the > same thing by just updating your permissions. When you add a new > permission you need to decide who receives the permission anyway. So you > already need to go into the permissions/groups interface to deal with at > least one group. The extra effort of assigning the permission to Portal > Admins as well is fairly negligible.
Additionally, I believe one of the safer ways to deploy a new channel, portlet, or tab is to begin by only granting it to the portal admin group (and possibly a QA group) in the first place. This allows the new content to be previewed in place by the admin/dev team before it's unleashed on the masses. Once it's in place and working in production as expected, then the permissions can be edited to include the appropriate audience. At that point, it's trivial to leave the admin group as an audience member for that new content. - Aaron -- Aaron Brown ([email protected] | 785-864-0462) University of Kansas Information Services System Design Enterprise System Integration Developer
smime.p7s
Description: S/MIME Cryptographic Signature
