How to open and share an alert
GitHub’s documentation distinguishes between opening an alert’s detail panel and navigating to its standalone page. To obtain the direct link:
- Navigate to your enterprise on GitHub.
- Select Security and quality at the top.
- Choose Public monitoring in the left sidebar.
- Find the relevant finding and click its alert number, rather than simply opening the detail panel.
- Bookmark the resulting page or copy its URL for a teammate who already has access. Each alert has its own unique URL.
There are important prerequisites: public monitoring must be enabled, and GitHub identifies enterprise owners and enterprise security managers as the roles that can access the page. It exists at enterprise level, not organization level. A shared link is therefore a route to an authorized view—not a way to grant access.
“Public monitoring” does not mean public alerts
The name describes where GitHub looks for exposed credentials. According to GitHub’s feature documentation, public monitoring extends visibility beyond enterprise-owned repositories to public repositories across GitHub, including non-code content such as issue and pull-request comments and gists. Findings are associated with an enterprise through membership or verified-domain email matching; enterprises using data residency rely on the latter rather than membership-roster matching.
The practical benefit is a simpler handoff. An investigator can point a colleague at one finding rather than describe which entry to locate in a filtered list. That is a workflow implication of the dedicated URL, not evidence that GitHub has changed detection or remediation capabilities.
A link helps triage; it does not fix the leak
The alert details include the exposed secret, attribution, its location and a Recommendations tab. That makes the dedicated page a useful destination for investigation.
But closing the paperwork is not closing the exposure. GitHub explicitly states that dismissing a public monitoring alert neither revokes the credential nor removes it from its public location; it also leaves any corresponding repository-level secret-scanning alert unchanged. Sharing, reviewing and dismissing are workflow actions—not credential remediation.