From 8eac0680b2240ef8e70b4d82a1e1a14aa36e1762 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Tue, 2 Jun 2026 22:27:09 +0000
Subject: [PATCH] docs: clarify datastore credential access in role-based
 access control

---
 security-and-compliance/role-based-access-control.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/security-and-compliance/role-based-access-control.mdx b/security-and-compliance/role-based-access-control.mdx
index 7f2d6d7..f749e4b 100644
--- a/security-and-compliance/role-based-access-control.mdx
+++ b/security-and-compliance/role-based-access-control.mdx
@@ -6,8 +6,8 @@ description: "Assign admin, developer, or viewer roles to team members with SSO
 Porter supports setting basic authorization permissions via for other members in a Porter project. At the moment, there are 3 roles that can be assigned in a Porter project:
 
 * **Admin:** read/write access to all resources, ability to delete the project and manage team members.
-* **Developer:** read/write access to applications, jobs, environment groups, cluster data, and integrations.
-* **Viewer:** read access to applications, jobs, environment groups, and cluster data.
+* **Developer:** read/write access to applications, jobs, environment groups, cluster data, datastores, and integrations. This includes reading datastore connection credentials (host, port, username, password).
+* **Viewer:** read access to applications, jobs, environment groups, and cluster data. Viewers cannot read datastore connection credentials.
 
 ## Adding Collaborators[](#adding-collaborators "Direct link to heading")