There are three distinct but related types of permissions:
-
Work Item Permissions, which apply to Collections, Channels, Discussions, and Task Lists.
-
Document Management Permissions, which apply to most item types.
-
Role-Based permissions, which apply to Projects. For more information about Role-based permissions and how they apply to Projects, see
Understanding Project Role Permissions .
Because different item types are governed by different permission types, permissions sometimes cannot transfer precisely when items are moved or copied. In such cases, Content Server must map, or translate, permissions from one type to another. For more information, see Permissions Mapping.
Work Item permissions apply to Channels, Collection objects, News items, Discussions, Topics and Replies, Task Lists and Tasks. The following rules apply:
The following table describes the four Work Item Permissions.
Work Item Permissions are inclusive. That is, if you have the Administer permission, you also have the Read and Write permission.
Permissions for Task Lists behave in a slightly different manner than for Channels or Discussions because they involve both the creator of the Task and its assignee, the user to whom the Task is assigned; therefore, the following applies:
-
If you have the Administer permission on a Task List, you also have full permissions on the Tasks it contains.
-
If you created the Task, and have Write permission on the Task List, you have full permissions on a Task. The Write permission on a Task List gives you permission to modify information for any Tasks it contains.
-
If you have Write permission on the Task List, and are the Tasks's assignee, you have partial permissions on a Task. This means that you can modify only the Comments and Status fields of that particular Task. You must have Write permission on a Task List before you can be assigned a Task within it.
Document Management Permissions
Document Management permissions apply to most items in Content Server, including Documents, Folders, and LiveReports. These permissions are more detailed than Work Item permissions and provide more precise control over the operations performed on items.
The following table describes each Document Management permission.
| Permission | With this permission . . . |
|---|---|
| See | You can see that the item exists in its Container, but you cannot open it to see its contents. |
| See Contents | You can open the item and see its contents. |
| Modify | You can rename the item and modify some of its properties. For Container items, such as Folders, this includes the properties that are listed on the item's Presentation tab on its Properties page. For more information, see Customizing Workspaces and Containers. |
| Edit Attributes | You can apply Categories to the item or modify the item's Categories or modify the attributes the Category contains. |
| Add Items | You can add items to the item. This permission is only available for Container items. |
| Reserve | You can reserve the item (to prevent other users from modifying it), modify it, and then unreserve the item. You can also add Versions to items you unreserve. This permission is only available for items that can be reserved. |
| Delete Versions | You can delete Versions of the item. The Delete Versions permission is only available for items that have Versions, such as Documents and Workflow Maps. |
| Delete | You can delete the item. |
| Edit Permissions | You can edit the permissions that other users or groups have on the item. |
All permissions are nested within the See permission. This means that, for example, you cannot modify or delete an item that you cannot see.
When you grant a permission, Content Server verifies that the base set of dependent permissions required for that permission are also selected. For example, as shown in the image below, if you select the Edit Permissions check box when no other check boxes are selected, Content Server automatically selects all the other check boxes and grants full permissions on the item.
