The following procedure shows how to set access rights to scenario folders.
Start the ACC and select Scenarios > Scenarios.
Select the scenario folder for which you want to define access.
Select File > Set Access Rights On Folder. The Set Access Rights dialog box appears.
The checkboxes show the different levels of access rights you can grant or remove:
List: Controls whether a this folder will appear as the result of a query. Note that, even if a user does not have List access, he or she could still access this folder by requesting it specifically.
Read: Controls the ability to view (but not add to or edit) this folder and its contents.
Write: Controls the ability to add or edit scenarios in this folder.
Delete: Controls the ability to remove this folder and its contents from the repository. This access right corresponds to the DESTROY access right in the Access Control List. For more information, see Secured Repositories in the ATG Repository Guide.
View owner: Controls the ability to view the name of the person who owns this folder, for example in the Author column of the Scenarios > Scenario window. Corresponds to READ-OWNER in the Access Control List.
Set owner: Controls the ability to change the owner of this folder. The owner access right exists essentially as a way of identifying the person or group who created the folder. Corresponds to WRITE-OWNER in the Access Control List.
View access rights: Controls the ability to view the access control list for this folder. (This access right is automatically granted to the owner of the folder.) Corresponds to READ-ACL in the Access Control List.
Set access rights: Controls the ability to change the access rights for this folder. (This access right is automatically granted to the owner of the folder.) Corresponds to WRITE-ACL in the Access Control List.
The list on the left shows the people for whom you can define access rights. The list can include individual users, organizations, roles, or profile groups. To add new items to this list, click Add, and select the items that represent the people for whom you want to define access. Remember that a member of an organization or a role inherits its access rights.
Use the checkboxes to grant or deny appropriate access rights for each user, organization, role, or profile group in the list on the left.
Important: Bear in mind a user’s access rights for content repositories as well as his or her access rights for scenario folders. For example, you might give a user write access to a specific scenario folder, but does he or she also need access to one or more content repositories? To create slot elements, for example, a user may need read access to a repository that stores image files. Make sure that users have access to all required content, and in particular, check that their access rights for different repositories do not conflict.
