Permissions overview
Repository owners, organization owners, security managers, and users with the admin role can:
- Create a security advisory for the repository.
- Access all security advisories for the repository.
- Add collaborators to the security advisory.
Collaborators have write permissions to the security advisory.
Collaborators with write permissions can't create a temporary private fork, with one exception: the reporter of a privately reported vulnerability can create one while they remain a collaborator on the security advisory. See Privately reporting a security vulnerability.
Repository security advisory collaborators without write access to the repository cannot create or view confidential comments. This restriction includes the reporter of a privately reported vulnerability unless they also have write access. See Managing privately reported security vulnerabilities.
Permission differences for global security advisories
Unlike repository security advisories, anyone can contribute to global security advisories in the GitHub Advisory Database at github.com/advisories. Edits to global advisories will not change or affect how the advisory appears on the repository. See Editing security advisories in the GitHub Advisory Database.
