In general, permissions refer to what actions (such as view, edit, delete, etc.) may be performed on what items by what users. Workflow allows us to enhance this, so that different permissions apply to items while they are in different states. For example, Reviewers can edit Engagements when they are in the Review state, but not when they are in the Archived state.

Note: an item (also referred to as object) is an instance of a content type. An item may be, for example, a single Engagement, or a single Entity. Each Engagement, each Entity, and each instance of all other types is, at any point in time, in a single discreet state.

Items do not inherit the state or workflow of their parents, since all items have their own type and their own state. The workflow of items is not affected by the state of any parent objects. For example, the set of actions that can be performed on a given Engagement by a given user are the same regardless of the state of the Entity (i.e., Active or Inactive) in which the engagement appears.

The tables in this section of the documentation give a detailed description of the permissions for each object type, in each state, for each role. Since Administrators can do everything, and Anonymous users can do nothing, they are not shown in these tables. TTW indicates Through the Web (or through the web browser interface); Go-Btwn indicates through the Go-Between.

In the charts below, hyphens indicate the action is not possible. In most cases where a hyphen is shown, it is in the Go-Btwn column and is because the functionality is not available in the Go-Between. Currently, the permissions are otherwise the same for the TTW and Go-Between interfaces in all cases. Y indicates the action is permitted, and N that it is not. The grey table cells are where an action is possible, and so all grey cells should contain either a Y, N or -.
 
In the tables, Set Properties refers to setting values in the Properties tab, such as keywords.

These tables assume the reserve/release system is not enabled.