> 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/17.latest/upgrading/version-specific.md). # Version Specific Upgrade Notes Version specific documentation for upgrading to new major versions of Umbraco Workflow. This page covers specific upgrade documentation for when migrating to Umbraco Workflow version 17. {% hint style="info" %} If you are upgrading to a new minor or patch version, you can find information about the breaking changes in the [Release Notes](/umbraco-workflow/17.latest/release-notes.md) article. {% endhint %} ## Version Specific Upgrade Notes History Version 17 of Umbraco Workflow has a minimum dependency on Umbraco CMS core of `17.0.0`. It runs on .NET 10. This version introduces granular permissions for Workflow features: * Active Workflows: Read * Advanced Search: Read * Alternate Versions: Create, Read, Update, Delete, Promote * Approval Groups: Create, Read, Update, Delete * Configuration: Read, Update * Content Reviews: Read * Document: Initiate, Unlock * History: Read * Release Sets: Create, Read, Update, Delete, Publish Default permissions are set in a migration: * Administrator group has all permissions * Editor group has all Read permissions * Other groups have no permissions Workflow settings (for content approval, content reviews and release sets) are relocated to the Settings section. Combined with the above permissions, this allows broader access to the Workflow section. Permission can be read-only for the views in the Workflow section (Approval Groups, Active Workflows, Content Reviews, History). ### Legacy version specific upgrade notes You can find the version specific upgrade notes for versions out of support in the [Legacy documentation on GitHub](https://github.com/umbraco/UmbracoDocs/tree/umbraco-eol-versions). --- # 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/17.latest/upgrading/version-specific.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.