# Workspace View Umbraco Workflow adds a [Workspace View](https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views) to all content nodes in the **Content** section where a workflow is enabled. The Workflow workspace view includes three sub-sections: * [Active Workflow](#active-workflow) * [Configuration](#configuration) * [History](#history) ## Active Workflow The Active workflow sub-section provides an interface for managing workflows for the current content node. When the current node is pending workflow approval, the **Active workflow** sub-section displays detailed information such as: * Option to [approve, reject, or cancel pending workflow tasks](#approve-reject-or-cancel-pending-workflow-tasks). * View change description and track differences across pending and completed workflows. * View the group responsible for approving the pending workflow. * View pending language variant(s) workflow. * View the workflow activity (eg. pending approval/task approvals/rejects) for the current workflow process. ![Active Workflow sub-section](https://2308063626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihjXeb5EgYW8vXPfbxLI%2Fuploads%2Fgit-blob-7abde933dfd0c39369c1c424d867bd714bc10e97%2FActive-Workflow-detailed-info-v14.png?alt=media) You can access Active Workflows from two places - the **Content** section and the **Workflow** section (depending on your user permission). Workflow Administrators (those users with access to the Workflow section) can access workflows assigned to a different group. In the **Workflow History**, these are noted as being performed by the admin. ### Approve, Reject, or Cancel pending workflow tasks #### Approve Workflow Tasks To approve a Workflow task, click on the **Approve** button in the Action section. #### Reject Workflow Tasks To reject a Workflow task, click on the **Reject** button in the Action section. Depending on the approval stage, the reviewer can decide where to send the rejected task. For first-stage approvals, the rejected task is sent back to the original editor/author. For second-stage approvals and above, the reviewer can send the rejected task either to the original editor or any other previous workflow group. ![Reject Workflow Tasks](https://2308063626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihjXeb5EgYW8vXPfbxLI%2Fuploads%2Fgit-blob-365b4969a4b790d77054264eece2c5b31aacf27f%2Fassign-rejected-task.png?alt=media) #### Cancel pending Workflow Tasks To cancel a pending Workflow task, click on the **Cancel** button in the Action section. ## Configuration The Configuration sub-section provides an interface for configuring the content approval flow for the current node. It also displays any Inherited or Document type approval flows applied to the current content node. In multi-lingual sites, each variant can have its own approval flow. By default, new variants inherit the configuration set on the default language. For example, German variants can be approved by the German speakers group, while English variants are approved by the English speakers group. ![Configuration sub-section](https://2308063626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihjXeb5EgYW8vXPfbxLI%2Fuploads%2Fgit-blob-b930d80dfa5cebbad3fd74c85f947a19f7d822b8%2FConfiguration-sub-section-v14.png?alt=media) ### Content Approval Flow You can add different groups for different stages of content approval flow. Content Approval flow groups can be reordered via drag and drop. You can also apply the approval flow either for publish and unpublish workflows or only publish workflow. ![Content approval flow](https://2308063626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihjXeb5EgYW8vXPfbxLI%2Fuploads%2Fgit-blob-43369a7cda369b00590b34008cf3ef6c71ffc911%2Fcontent-approval-flow-v14.png?alt=media) #### Approval Flow Types Approval Flows are available in three types: Content approval flow, Inherited approval flow, and Document type approval flow. A given content node may have all three approval flow types applied but only one will be applied as per the following order of priority: | Flow Type | Description | Priority | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | | **Content approval flow** | Set directly on a content node via the **Configuration** section in the **Workflow** tab. | Highest | | **Document type approval flow** | Set in the **Settings** section. Applies to all content nodes of the selected Document Type unless overridden by a Content approval flow set directly on the node. Requires a license. | Secondary | | **Inherited approval flow** | Used when a content node has no Content approval flow set, nor a flow applied to its Document Type. Umbraco Workflow will traverse the content tree upwards to find a Content approval flow. | Lowest | ![Approval Flow Types](https://2308063626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihjXeb5EgYW8vXPfbxLI%2Fuploads%2Fgit-blob-43369a7cda369b00590b34008cf3ef6c71ffc911%2Fcontent-approval-flow-v14.png?alt=media) Review the current Permissions for Approval Groups in the **Approval Groups** section for **Node-based approvals** and **Document type approvals** only. For more information see the [Roles](https://docs.umbraco.com/umbraco-workflow/workflow-section/approval-groups#roles) section in the [Approval Groups](https://docs.umbraco.com/umbraco-workflow/workflow-section/approval-groups) article. ![Approval Groups Roles](https://2308063626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihjXeb5EgYW8vXPfbxLI%2Fuploads%2Fgit-blob-911c1dba8503123382fda8fabf68de107db394f6%2Fapproval-groups-roles-v14.png?alt=media) Document type approval flows may contain conditional stages, such as including **Translators** in the workflow only when the **Description** property has changed. For more information on settings conditions in Document type approval flows, see the [Document type approval flows](https://docs.umbraco.com/umbraco-workflow/getting-started/broken-reference) section in the [Workflow Settings](https://docs.umbraco.com/umbraco-workflow/getting-started/broken-reference) article. Configuration cannot be modified when a content node is in a workflow process. #### Content reviews Content reviews is a tool that allows content editors to keep their content up-to-date. For more information, see the [Content reviews](https://docs.umbraco.com/umbraco-workflow/workflow-section/content-reviews) section. ![Content reviews](https://2308063626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihjXeb5EgYW8vXPfbxLI%2Fuploads%2Fgit-blob-7a3c7878f53572ef1a34f9f9e552c07a59e71919%2FContent-reviews-v14.png?alt=media) ## History The History sub-section provides a chronological audit trail of workflow activity for the current node. It displays a table containing the following information: * Type of Publish * Who the workflow is requested by * The date the workflow was requested * Comments ![History sub-section](https://2308063626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihjXeb5EgYW8vXPfbxLI%2Fuploads%2Fgit-blob-7c4d0c402d74d99d53b89c609313c7af9427af7e%2FHistory-sub-section-v14.png?alt=media) You can also **Filter** the records based on the information listed above. Additionally, you can adjust the total number of records displayed on a page. The **Detail** button at the end of the record displays an overlay with content similar to the Active workflow sub-section. ![Details overlay](https://2308063626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihjXeb5EgYW8vXPfbxLI%2Fuploads%2Fgit-blob-cfe50524e201ebbc95695b977a9635dee152c6ff%2FWorkflow-Content-app-Details-overlay-v14.png?alt=media)