Permissions in KM Repositories 
Use
Permissions define which users have which access rights for items in KM repositories (folders, documents, and links).
For information on permissions for
items in the Portal Content Directory (PCD), see 
Portal
Permissions.
Prerequisites
You need read permission for the item in question in order to display its permissions.
You must be entered in the list of permission owners in order to change the permissions.
Features
There are two types of permission in Knowledge Management:
· Permissions (for the item itself)
These permissions define permission to read, write, and delete items.
You can set the permissions for all items (folders, documents, links).
· Service Permissions
Service permissions define permissions for functions that are provided by KM services, such as subscriptions.
You can only set service permissions for folders.
Access Control Lists
An access control list (ACL) specifies which users, groups, or roles have which access permissions for items.
An entry in the access control list specifies an access permission such as read and a user, group, or role.
There are separate access control lists for permissions and service permissions. This is particular important for inheritance.
Inheritance
In the folder hierarchy of a KM repository, permissions are inherited by subordinate folders from superordinate folders.
When you create a new item in a KM folder, the item initially has no access control list. Instead, it inherits the permissions of the superordinate folder.
When you change and save the permissions, the system creates a separate ACL for the item in question. Inheritance no longer takes place. From this point on, changes to the permissions of the superordinate folder are no longer inherited by the subordinate object.
When an object inherits the permissions of a superordinate folder, a comment indicates that this has happened on the Permissions or Service Permissions tab.
See also:
Permissions (for the item itself)