From aae1370f806f42ef9ddc7a82a04fac661eb8a722 Mon Sep 17 00:00:00 2001
From: Dhruval Anandkar <155497084+DhruvalAnandkar@users.noreply.github.com>
Date: Sun, 12 Jul 2026 23:22:03 -0400
Subject: [PATCH] docs: propose note about custom runner group UI visibility

Adds a note clarifying that organization runners in custom groups may not render in legacy repository settings, despite retaining full routing access, to prevent user confusion.
---
 .../manage-runners/self-hosted-runners/manage-access.md     | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/content/actions/how-tos/manage-runners/self-hosted-runners/manage-access.md b/content/actions/how-tos/manage-runners/self-hosted-runners/manage-access.md
index a4014197c326..676ed35f1c54 100644
--- a/content/actions/how-tos/manage-runners/self-hosted-runners/manage-access.md
+++ b/content/actions/how-tos/manage-runners/self-hosted-runners/manage-access.md
@@ -56,6 +56,12 @@ For runner groups in an enterprise, you can change what organizations in the ent
 
 For runner groups in an organization, you can change what repositories in the organization can access a runner group.
 
+{% note %}
+
+**Note:** Some users have reported that organization-level runners assigned to custom runner groups don't appear on the legacy **Settings > Actions > Runners** page for individual repositories, even when the group has valid repository access configured. If a runner you expect to see is missing there, check the repository's **Actions > Runners** management page, which reflects custom group membership more reliably.
+
+{% endnote %}
+
 {% data reusables.actions.runner-groups-org-navigation %}
 {% data reusables.actions.changing-repository-access-for-a-runner-group %}