Limiting the Visibility of Portal Publish Locations

An administrator can limit the visibility of portal Publish Locations for the Publish to Astoria Portal command using Role Group membership definitions.

For each target location whose visibility is to be limited, an administrator must define a Role of the exact same name.

Note: The name is case sensitive, so if the target Publish Location is Stage and the Role definition is stage (lower-case), the Stage location will always be a selectable Publish Location. If the Role definition is Stage, the Stage Publish Location will be visible only to users who have been added as members of the Stage Role.

Role Groups can be inherited, so Role membership can be defined at an appropriate level within the repository, such as at the Cabinet or a folder location (such as in translation cabinets). Membership can also be defined at the Global or Backstop levels.

Role Group or user members are defined on a repository object using the Define Access Controls command's Roles tab. Select the Role Group name and Add it to the Present pane. Then with that name selected, add users or groups to the Present panes and click OK. See Assigning Role Membership.

When a user issues the Publish to Astoria Portal command on an on object that inherits the Role membership, they can select a Publish Location for which they are authorized, or one that is not limited by Role membership.

Tip: A user can see if or how a user or group enjoys the required Role Group membership on a repository object. Select the object and issue the Define Access Controls command. Click the Roles tab and select the Role Group name to display the users or groups who are members of the Role for that object or inherit membership. Only authorized users will see the desired publishing location, as identified by the Role name.