From a21d8214e4299f392fde4cead032cdf61de3b537 Mon Sep 17 00:00:00 2001 From: Ramandeep Singh Makkar Date: Fri, 30 Jan 2026 18:01:26 +0530 Subject: [PATCH] Update note on organization membership visibility Clarify that private repositories and contributions remain inaccessible even if the organization is public on GitHub. --- .../publicizing-or-hiding-organization-membership.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/account-and-profile/how-tos/organization-membership/publicizing-or-hiding-organization-membership.md b/content/account-and-profile/how-tos/organization-membership/publicizing-or-hiding-organization-membership.md index 20fbbef72471..20c193875c7f 100644 --- a/content/account-and-profile/how-tos/organization-membership/publicizing-or-hiding-organization-membership.md +++ b/content/account-and-profile/how-tos/organization-membership/publicizing-or-hiding-organization-membership.md @@ -29,3 +29,5 @@ contentType: how-tos * To hide your membership, choose **Private**. ![Screenshot of an entry in the list of organization members. Next to the username, a dropdown menu, labeled "Private", is outlined in dark orange.](/assets/images/help/organizations/member-visibility-link.png) + +Note: Making an organization public on your profile in GitHub does not mean its private repositories and your contributions to them become visible. Private repositories remain private and can only be accessed by organization members or collaborators who have been explicitly granted permission, regardless of the organization’s public profile status.