From ad3ca9acf84a01114490b30c47eb97137ac89923 Mon Sep 17 00:00:00 2001 From: AlanCoding Date: Tue, 17 Jan 2017 09:40:31 -0500 Subject: [PATCH] Incorporate more feedback about RBAC logic regarding node deletion --- docs/workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/workflow.md b/docs/workflow.md index 0843dee289..dee731264d 100644 --- a/docs/workflow.md +++ b/docs/workflow.md @@ -61,7 +61,7 @@ Workflow jobs cannot be copied directly, instead a workflow job is implicitly co * Workflow job read and delete permissions follow from its associated workflow job template. * Workflow job relaunch permission consists of the union of execute permission to its associated workflow job template, and the permission to re-create all the nodes inside of the workflow job. * Workflow job template nodes rely their permission rules on the permission rules of both their associated workflow job template and unified job template for creation and editing. - * Workflow job template nodes can be deleted with permission to their workflow job template (even lacking permission to its job template). + * Workflow job template nodes can be deleted with admin permission to their workflow job template (even lacking permission to the node's job template). * Workflow job nodes are viewable if its workflow job is viewable. * No CRUD actions are possible on workflow job nodes by any user, and they may only be deleted by deleting their workflow job. * Workflow jobs can be deleted by superusers and org admins of the organization of its associated workflow job template, and no one else.