GitHub announced that its security advisory permissions feature is now generally available. Organization owners can assign custom repository roles that allow users to manage security advisories, including private vulnerability reports, without granting full administrator privileges.
What is new
The new permissions are part of GitHub’s custom repository roles system. A role can now include ‘security advisory read’, ‘security advisory write’ and ‘security advisory triage’. ‘Read’ lets users view vulnerability reports, ‘write’ permits editing of advisories, and ‘triage’ enables labeling and prioritising reports. Previously, only repository administrators could perform these actions.
What this means
Teams can delegate advisory work while keeping admin rights limited, reducing the chance of accidental configuration changes. The feature is enabled in the repository settings under ‘Roles & permissions’ and does not incur additional cost. Existing organizations need to enable the new roles manually; new organizations receive them by default.



