> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-workflow/getting-started/workflow-workspace-view.md). # 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 two sub-sections: * [Configuration](#configuration) * [History](#history) ## 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://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%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://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%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://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%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](/umbraco-workflow/workflow-section/approval-groups.md#roles) section in the [Approval Groups](/umbraco-workflow/workflow-section/approval-groups.md) article. ![Approval Groups Roles](https://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%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://github.com/umbraco/UmbracoDocs/blob/main/17/umbraco-workflow/getting-started/content-approval-settings.md#document-type-approval-flows) section in the [Content approval settings](https://github.com/umbraco/UmbracoDocs/blob/main/17/umbraco-workflow/getting-started/content-approval-settings.md) 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](/umbraco-workflow/workflow-section/content-reviews.md) section. ![Content reviews](https://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%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://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%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 Workflow Detail dialog. ![Details overlay](https://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%2Fuploads%2Fgit-blob-cfe50524e201ebbc95695b977a9635dee152c6ff%2FWorkflow-Content-app-Details-overlay-v14.png?alt=media) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.umbraco.com/umbraco-workflow/getting-started/workflow-workspace-view.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.