Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,38 @@ Collaborators with write permissions can't create a temporary private fork, with

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 [AUTOTITLE](/code-security/how-tos/report-and-fix-vulnerabilities/fix-reported-vulnerabilities/manage-vulnerability-reports#discussing-a-report-with-people-who-have-write-access).

{% ifversion ghec %}

### Permissions from custom repository roles

Organizations that use custom repository roles can let people work on repository security advisories without making them repository administrators or security managers. Add one or more of these permissions to a custom repository role. See [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/about-custom-repository-roles).

* **View security advisories**: view draft security advisories, their status, and comments, but not confidential comments or the advisory's event history.
* **Create, edit, and manage security advisories**: everything in "View security advisories", plus create and edit security advisories, comment, manage collaborators, and create a temporary private fork.
* **Accept private vulnerability reports and close or reopen security advisories**: requires one of the permissions above.
* **Publish security advisories and request CVEs**: requires one of the permissions above.

Action | View | Create, edit, and manage | Accept, close, or reopen | Publish and request CVEs |
------ | ---- | ------------------------ | ------------------------ | ------------------------ |
See draft security advisories | {% octicon "check" aria-label="Yes" %} | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} |
Create and edit security advisories, comment, and manage collaborators | {% octicon "x" aria-label="No" %} | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} |
Create a temporary private fork | {% octicon "x" aria-label="No" %} | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} |
Accept a private vulnerability report, or close or reopen a security advisory | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "check" aria-label="Yes" %}¹ | {% octicon "x" aria-label="No" %} |
Publish a security advisory or request a CVE | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "check" aria-label="Yes" %}¹ |
Merge changes from a temporary private fork | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %}² |

¹ Only together with "View security advisories" or "Create, edit, and manage security advisories". Without one of them, these permissions grant no access.

² Merging changes from a temporary private fork still requires a repository administrator or security manager, even if a custom role includes all of these permissions.

When someone with "Create, edit, and manage security advisories" creates a temporary private fork, they are added as a collaborator on the security advisory so they can work in the fork. They remain a collaborator until they are removed, even if the custom role changes. Other people need to be added as collaborators to create pull requests in the fork.

People with these permissions can't delete a temporary private fork. Confidential comments are only available to people with "Create, edit, and manage security advisories" who also have write access to the repository.

People with "View security advisories" or "Create, edit, and manage security advisories" who watch the repository are notified about new draft security advisories and private vulnerability reports.

{% endif %}

### Permission differences for global security advisories

Unlike repository security advisories, anyone can contribute to **global security advisories** in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories). Edits to global advisories will not change or affect how the advisory appears on the repository. See [AUTOTITLE](/code-security/how-tos/report-and-fix-vulnerabilities/fix-reported-vulnerabilities/edit-advisory-database).
Expand Down
9 changes: 9 additions & 0 deletions data/reusables/organizations/additional-permissions.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,15 @@ For more information, see [AUTOTITLE](/repositories/configuring-branches-and-mer
* Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}
* View {% data variables.product.prodname_secret_scanning %} alerts
* Dismiss, reopen, or assign {% data variables.product.prodname_secret_scanning %} alerts
{%- ifversion ghec %}
* View security advisories
* Create, edit, and manage security advisories
* Includes "View security advisories"
* Accept private vulnerability reports and close or reopen security advisories
* Requires "View security advisories" or "Create, edit, and manage security advisories"
* Publish security advisories and request CVEs
* Requires "View security advisories" or "Create, edit, and manage security advisories"
{%- endif %}

{%- ifversion ghec %}
### Actions
Expand Down
Loading