From c3dd1e99c2978d618e7e7b1155cbde88767b9376 Mon Sep 17 00:00:00 2001
From: Deepu Issac Martin <82010309+deepumrtn@users.noreply.github.com>
Date: Mon, 28 Jul 2025 01:38:21 -0700
Subject: [PATCH] Update the documentation to state that outside collaborators
 must be added to the upstream repositories before they can be added to
 private forks (#56862)

---
 .../about-permissions-and-visibility-of-forks.md            | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks.md
index 62b4d1af04..b0c4db3831 100644
--- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks.md
+++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks.md
@@ -14,7 +14,10 @@ topics:
 
 {% data reusables.repositories.you-can-fork %}
 
-If you fork a private repository that belongs to a personal account, external collaborators also get access to the fork. If you fork a private {% ifversion ghec or ghes %}or internal {% endif %}repository that belongs to an organization, teams within the organization get access to the fork, but external collaborators do not. You can add an external collaborator to a fork of a private repository that belongs to an organization if you are an owner of that organization or if your organization allows repository administrators to invite external collaborators.{% ifversion ghec or ghes %} You can add an external collaborator to a fork of an internal repository that belongs to an organization if the external collaborator also has access to the upstream repository.{% endif %}
+* If you fork a private repository that belongs to a personal account, external collaborators also get access to the fork.
+* If you fork a private {% ifversion ghec or ghes %}or internal {% endif %}repository that belongs to an organization, teams within the organization get access to the fork, but external collaborators do not.
+* {% ifversion ghes %} You can add an external collaborator to a fork of a private repository that belongs to an organization if you are an owner of that organization or if your organization allows repository administrators to invite external collaborators.{% endif %}{% ifversion fpt or ghec %} You can add an external collaborator to a fork of a private repository owned by an organization if you are an organization owner, or if your organization allows repository administrators to invite external collaborators, and the external collaborator also has access to the upstream repository.{% endif %}
+{% ifversion ghec or ghes %} * You can add an external collaborator to a fork of an internal repository that belongs to an organization if the external collaborator also has access to the upstream repository.{% endif %}
 
 {% ifversion fpt or ghec %}
 
@@ -64,6 +67,7 @@ If you work with forks, or if you're the owner of a repository or organization t
 ### About forks within an organization
 
 Forks within the same organization copy the collaborators and team settings of their upstream repositories. If a repository is owned by an organization:
+
 * That organization controls the permissions of its forks.
 * Any teams from the upstream permission structure that exist and are visible in the target organization or user namespace will have their permissions copied.
 * Admin permissions remain with the upstream owner, except when a user forks into a different organization.