> 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/workflow-section/content-reviews.md). # Content Reviews Content reviews is a tool that allows content editors to keep their content up-to-date. **Content reviews** adds a new dashboard to the **Workflow** section. By default, Content reviews are disabled and can be enabled from **Content reviews Settings** in the **Workflow** section. ![Enable Content Reviews](https://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%2Fuploads%2Fgit-blob-af1f4b37517a0724e99159ee13facf18797a49e9%2FEnable-content-reviews-v14.png?alt=media) ## Video overview {% embed url="" %} Watch this video to learn how to use the Content Review feature in Umbraco Workflow {% endembed %} ## Content Reviews Dashboard The Content Reviews Dashboard provides an overview of the expired content. The dashboard displays a table containing the following details: * Page name/Node with the Language variant * Next review due date * Last reviewed date * Review period in days * Review group ![Content Reviews Dashboard](https://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%2Fuploads%2Fgit-blob-e99aa91a0628d82ece6239501b300e4144513c6e%2FContent-review-dashboard-v14.png?alt=media) Selecting a content node takes you to the content node in the **Content** section, where you can see the Content review dialog. The Content review dialog is displayed only when the node has passed its review date. Also, the review dialog is displayed only to users assigned as reviewers for the node. For more information, see the [Content Reviews Permissions](/umbraco-workflow/getting-started/content-review-settings.md#content-review-permissions) section ![Content Review Message Banner](https://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%2Fuploads%2Fgit-blob-0b0aa54e4cafd9d8e88062000f9f06ae522b6742%2Fcontent-review-message-banner-v14.png?alt=media) Clicking on **Mark as reviewed** allows the review group member to mark the content as reviewed. Optionally, the review group member can also set the next review date on the content node. The next review date must fall inside the review period set in the **Content Reviews Settings**. ![Content Review Date](https://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%2Fuploads%2Fgit-blob-f51e5fc0ae6e49ff08bc532057d14a4d55ef8343%2Fcontent-review-date-v14.png?alt=media) You can also **Filter** the records based on the Document Type, Review Group, Next review due date, Last reviewed date, and Expired review Status. ![Content Reviews Filters](https://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%2Fuploads%2Fgit-blob-7e26e61ceaa34b56410e73caedd27a38714e5577%2Fcontent-reviews-filter-v14.png?alt=media) Additionally, you can adjust the total number of records displayed on a page. ![Content Reviews PageSize](https://1513306126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FonwuUOTAf576n6UVv16T%2Fuploads%2Fgit-blob-249401a205882accba35e3f6bbf0809f67031218%2Fcontent-reviews-pagesize-v14.png?alt=media) Read the [Content Review Settings](/umbraco-workflow/getting-started/content-review-settings.md) article to learn how to configure reviews. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.umbraco.com/umbraco-workflow/workflow-section/content-reviews.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.