From b64d612c4dcbfa5918e8262cdfd230be3bc00d03 Mon Sep 17 00:00:00 2001
From: sheltongraves <148902861+sheltongraves@users.noreply.github.com>
Date: Tue, 13 May 2025 16:26:10 -0400
Subject: [PATCH] Merge pull request #22491 from sheltongraves/patch-13

Update roles-and-permissions.md
---
 content/manuals/security/for-admins/roles-and-permissions.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/manuals/security/for-admins/roles-and-permissions.md b/content/manuals/security/for-admins/roles-and-permissions.md
index f2464db71f..5a8a969493 100644
--- a/content/manuals/security/for-admins/roles-and-permissions.md
+++ b/content/manuals/security/for-admins/roles-and-permissions.md
@@ -20,6 +20,7 @@ When you invite users to your organization, you assign them a role. A role is a
 The following roles are available to assign:
 
 - Member: Non-administrative role. Members can view other members that are in the same organization.
+- Distributor Member: Restricted-access role. Distributor Members can only view and pull from repositories they’ve been explicitly granted access to. They cannot view other members or teams.
 - Editor: Partial administrative access to the organization. Editors can create, edit, and delete repositories. They can also edit an existing team's access permissions.
 - Organization owner: Full organization administrative access. Organization owners can manage organization repositories, teams, members, settings, and billing.
 - Company owner: In addition to the permissions of an organization owner, company owners can configure settings for their associated organizations.