Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update permissions.md #2315

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions pages/pipelines/permissions.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find this quite hard to parse. Could you try expanding it a bit more or perhaps providing an example? Thinking like:

Note that team-level permissions override member permissions. For example, if the same user has a team level permission to X on a pipeline but only a X member permission on that pipeline, they can...


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`):
Expand Down