From 29128686c2617edb6de4c565fd21db2f14da97e8 Mon Sep 17 00:00:00 2001 From: stephanieatte <122297064+stephanieatte@users.noreply.github.com> Date: Wed, 19 Jul 2023 10:13:50 -0600 Subject: [PATCH] Update permissions.md Ticket: https://secure.helpscout.net/conversation/2286383801/53474/ The customer was confused about permissions for teams and pipelines. Its best to clarify about the order the precedence so they know the expected behaviour --- pages/pipelines/permissions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pages/pipelines/permissions.md b/pages/pipelines/permissions.md index 4992d194d3..50c6fba5e3 100644 --- a/pages/pipelines/permissions.md +++ b/pages/pipelines/permissions.md @@ -135,6 +135,8 @@ From the Member Permissions page, organization admins can toggle whether or not If your organization has teams enabled, the pipeline creation permissions are managed at a team level. Pipeline creation permission controls can be found on the Teams Settings page. Without teams enabled, the pipeline creation permission control can be found on the Member Permissions page. +Note: The Team-Level permissions on a given pipeline, will override the lower priviledge member permisions in the team settings. + Organization admin can delete organization members. To delete organization members using GraphQL, the admin needs to: 1. Find the `id` for the user to be deleted (in this example `Jane Doe`):