From 28d056cf7a20b2abc32a3571b21eb9e30fdbfa82 Mon Sep 17 00:00:00 2001 From: Scott Wilson Date: Fri, 18 Apr 2025 09:54:58 -0700 Subject: [PATCH] documentation: correct developer description --- .../platform/access-controls/role-based-access-controls.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/platform/access-controls/role-based-access-controls.mdx b/docs/documentation/platform/access-controls/role-based-access-controls.mdx index 9d1170f69..341c20868 100644 --- a/docs/documentation/platform/access-controls/role-based-access-controls.mdx +++ b/docs/documentation/platform/access-controls/role-based-access-controls.mdx @@ -25,7 +25,7 @@ By default, every user in a project is either a **viewer**, **developer**, or an As such: - **Admin**: This role enables identities to have access to all environments, folders, secrets, and actions within the project. -- **Developers**: This role restricts identities from performing project control actions, updating Approval Workflow policies, managing roles/members, and more. +- **Developers**: This role restricts identities from performing project control actions, updating Approval Workflow policies, managing roles, editing and removing project members, and more. - **Viewer**: The most limiting bulit-in role on the project level – it forbids user and machine identities to perform any action and rather shows them in the read-only mode. ![Project member role](/images/platform/access-controls/rbac.png)