From cca4181f2811a69973985565aba657a8045decf2 Mon Sep 17 00:00:00 2001 From: Jamie Howard Date: Wed, 13 Sep 2023 16:57:28 +0100 Subject: [PATCH] chore(docs): RBAC for stages in content manager docs --- .../docs/01-core/content-manager/02-review-workflows.mdx | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/docs/docs/01-core/content-manager/02-review-workflows.mdx b/docs/docs/docs/01-core/content-manager/02-review-workflows.mdx index 4f5a3ddff3..447c262bec 100644 --- a/docs/docs/docs/01-core/content-manager/02-review-workflows.mdx +++ b/docs/docs/docs/01-core/content-manager/02-review-workflows.mdx @@ -8,7 +8,7 @@ tags: ## Summary -Review workflows are disabled for all content-types by default and have to be enabled for each of them individually. More about how to +Review workflows are disabled for all content-types by default and have to be enabled for each of them individually. More about how to [enable review-workflows for a content-type](/docs/settings/review-workflows#edit--create-view). The feature itself is visible in two places of the content-manager: list and edit view. @@ -37,18 +37,17 @@ Please refer to the [type definitions](/settings/review-workflows) for more info **Note**: Downgrading from EE to CE won't delete the associated review workflow data and `http://localhost:1337/content-manager/content-types` still returns true. The admin app had to add an additional check if the feature toggle returned in `http://localhost:1337/admin/project-type` is enabled. - ### Edit view If the feature is enabled on the current content-type, the selected stage will show up in the information sidebar next to the edit view. Users -can select any other stage of the current workflow. +can select any other stage of the current workflow provided they have the necessary permissions to change the current stage see [EE Review Workflows](../admin/01-ee/01-review-workflows.md). Stage assignments are decoupled from entities, meaning updating entity attributes won't set the selected stage at the same time. Instead the stage select component will trigger an atomic update on the admin API to assign/ update a stage to the current entity. Because of this decoupling, stages **can not be assigned on entity creation** and only after they have been created. -The information which stage is currently assigned to an entity is send as part of the entity response payload in the attribute `strapi_stage`. +Information about which stage is currently assigned to an entity is sent as part of the entity response payload in the attribute `strapi_stage`. Please refer to the [type definitions](/settings/review-workflows) for more information. ```ts