Granting Access Permissions on Repository Items

The repository administrator or a user with Full permission on a document can grant permissions on it from the Permissions tab of its repository property sheet. You can grant permissions on the repository root, folders, PowerDesigner models and model packages, and external application files, but not on individual model diagrams or objects.

In order for a user to check documents out of and into the repository, she must have the following permissions:

Check out - Read permission. When you create a user, she is inserted into the Public group, which by default is granted Read permission on the repository root.
First check in (to create a document in the repository) or creating a folder - Write permission on the target location (the repository root or a folder).

The user who creates a repository item has, by default, Full permission over it, though this permission can be reduced by an administrator. Other permissions are cascaded down from the parent folder or root, so that if another user has Write permission on the parent folder, then he will have Write permission on the new item.
Subsequent check ins (to update an existing document) - Read permission on the target location and Write permission on the document (including, for PowerDesigner models, all impacted packages).

Note: Object permissions should be viewed in conjunction with the rights granted to users or groups (see Granting Rights to Users and Groups). For examples of granting rights and permissions, see Controlling Repository Access.

Right-click the item in the Repository Browser, and select Permissions to open the item's property sheet at the Permissions tab.
Click the Add tool to open a list of available users and groups, select one or more, and click OK to add them to the list.
For each user or group, select the permission you want to grant in the Granted Permission column. The following permissions are available:
- List - To view the item in the browser and in search results, and display read-only property sheets.
  
  Note: Users who do not have even this permission on a document or folder cannot even see it in the repository Browser.
- Read - To have all the List permissions, and also compare documents, and check the document (or folder contents) out from the repository.
- Write - To have all the Read permissions, and also check in, freeze, and lock document versions.
- Full - To have all the Write permissions, and also manage permissions granted to users or groups and remove locks on documents.
[optional] Click the Copy Permissions to All Children tool to propagate changes to the item's children.

When you create a folder or check in a model or project, the permissions defined on its parent are propagated to it. However, subsequent changes made to the permissions for the parent are not applied to its children unless you click this tool. For example, if a you grant write permissions to the Major Project folder, to the Development Team 2 group, then they will not automatically be granted write access on its contents.
[optional] Click the Show All Authorized Users tool to display all the users and groups who have a permission on the item, including those inheriting permissions from groups.

Consult the read-only Effective Permission column to see the highest level of permission that each user or group has either directly or via a group. A user who has no directly granted permission on an item may inherit a Write permission by virtue of membership in a group, and will appear in the list when the Show All Authorized Users tool is pressed.

Note: If you delete a group from the list while the Show All Authorized Users tool is pressed, it and its members remain visible in the list with their granted and effective permissions reduced to <none>, until you click Apply or OK.
Click OK to save your changes.