Setting Permissions in the Permission Editor 

Use

Use the Permission Editor to set user access and control permissions to portal components, folders and objects in the Portal Catalog.

In the Assign New Permission area, you search for the user, role or group to that you want to assign permissions to. Then, in the Assign Permissions area, you define the permission details.

Permissions are automatically passed from a folder to the sub-folders and unit objects in it. Unit objects then pass their permissions to their embedded child objects, and so on. To set different permissions for objects within a folder, you need access the objects specifically and modify their permissions, as needed. For more information, see Permission Inheritance Model.

 

Prerequisites

You have launched the Permission Editor and selected the object whose permissions you want to set or edit. See Launching the Permission Editor.

 

Procedures

Assigning New Permissions

...

       1.      Under Assign New Permissions, locate the user, role or group that you want to assign permissions to:

                            a.      In the Search for box, enter keywords to search for. You may use the wildcard symbol (*) in the search string. For example: enter Ethan* for all users whose first name is Ethan.

                            b.      In the Search in drop-down list, choose the category in which to perform the search. Your options are: Users, Groups, or Roles.

                            c.      Choose Go. The results of the search query are displayed in a list below the search area.

You can use the Permission Source button at the bottom of the screen to display the permissions of its closest ancestor object:

§         If the object has assigned permissions, the permissions of the closest ancestor object will be display only. This is useful before using the Restore Permissions option (see Restoring Permission Inheritance).

§         If the current object does not have assigned permissions (so that it inherits its permissions), you will be able to edit the permissions of the displayed ancestor objects. Any changes you make to the permissions of the course object will be inherited by the current object.

       2.      Add the users, groups, or roles you have located to the Assigned Permissions area. To do this, proceed as follows:

                            a.      In the Assign New Permissions area, choose the user, group, or role you want to add.

                            b.      Click Add. The user, group, or role is now displayed in the Assigned Permissions area.

       3.      In the Assigned Permissions area, define the permission levels for the listed users, groups, or roles:

                            a.      To provide a user/group/role with design-time authorization, in the Administrator column, choose a permission level from the drop-down list. For information on the available permissions levels, see Permission Levels.

                            b.      To provide a user/group/role with run-time authorization, in the End User column, select the check box.

                            c.      If you currently editing permissions to a role object (in an object-specific Permission Editor), you can authorize a user/group/role to perform role assignments to a current role. To do so, select the check box in the Role Assigner column.

 

For information about setting permissions to security zones, see Security Zones.

       4.      Repeat the previous steps to assign permissions to additional users, groups, or roles for the object or folder you are currently editing.

       5.      In the tools area at the top, choose Save.

Removing User-Assigned Permissions

...

       1.      In the Assigned Permissions area, select the user, group, or role

       2.      Choose Remove.

       3.      In the tools area at the top, choose Save.

 

Result

You have assigned users, groups or roles permission to access the selected object or folder.

The combination of Administrator: none, End User: disabled, and Role Assigner: disabled for a particular user/group/role in an object implies that the user/group/role has no administrator or end user permission for the given object. When you save or refresh the user interface, the user/group/role will be automatically removed from the Assigned Permissions list.