> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/ignore-issues/ignore-approval-workflow.md).

# Ignore Approval Workflow

How the Ignore Approval Workflow adds governance around risk acceptance in Snyk Code

Ignore Approval Workflow creates a layer of governance around risk acceptance within Snyk. You can perform the following:

* Request ignores for specific findings from developer workflows (CLI, IDE, and API).
* Approve or reject ignore requests before ignores are applied.
* Apply access controls and audit user actions.
* Notify users about new ignore requests pending approval and changes in request status.

{% hint style="info" %}
Ignore Approval Workflow supports Snyk Code. Snyk does not support consistent\
ignores for Snyk OS, Snyk Container, and Snyk IaC.
{% endhint %}

## Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* ​[Enable Snyk Code Consistent Ignores](https://docs.snyk.io/manage-risk/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code#enable-snyk-code-consistent-ignores) as the Ignore Approval Workflow does not process other types of ignores. Any existing ignores persist as approved ignores if the Ignore Approval Workflow is enabled.
* ​Disable DeepCode inline Code ignores. Existing inline Code does not persist when the Ignore Approval Workflow is enabled. DeepCode inline ignores, which are behind a feature flag and not publicly documented, need to be disabled.
* Ignore Approval Workflow is supported on the following versions of Snyk CLI and IDE:
  * Snyk CLI v1.1299.1
  * Snyk IDE
    * Visual Studio Code v2.24.0
    * JetBrains v2.16.0
    * Eclipse v3.4.0
    * Visual Studio v2.4.0

## Enabling Ignore Approval Workflow

You can enable Ignore Approval Workflow at the Organization-level settings as follows:

1. Log in to the Snyk Web UI and select your [Group and Organization](https://docs.snyk.io/snyk-platform-administration/groups-and-organizations).
2. Navigate to **Organization** > **Settings**.
3. Enable **Ignore Approval Workflow for Snyk Code**.

Ensure Code Consistent Ignores is enabled for this Snyk Organization as well, since it is a prerequisite for Ignore Approval Workflow.

{% hint style="info" %}
Ignore Approval Workflow cannot be enabled at the Group level. An\
Organization-level API is available to enable it, so Groups with many\
Organizations can enable the feature at scale.
{% endhint %}

{% hint style="info" %}
When Ignore Approval Workflow is disabled, any pending ignore requests are canceled. Resubmit these ignores.
{% endhint %}

## Ignore Approval Workflow features <a href="#ignore-approval-workflow-features" id="ignore-approval-workflow-features"></a>

### Create and review ignore requests <a href="#create-and-review-ignore-requests" id="create-and-review-ignore-requests"></a>

Users can create and view ignore requests through the CLI, IDE, and API. Users with the reviewer permission can review and ignore requests through the UI on a new Ignore request page. Ignores are no longer automatically created, but instead a user can create an ignore with the status of `Pending` that can then be approved or rejected by reviewers. Requesters must provide a reason for their ignore request submission.

After a reviewer approves or rejects a request, you cannot edit the ignore reason. You can still edit the ignore type and expiration.

### Notifications <a href="#notifications" id="notifications"></a>

Reviewers get an email notification when someone creates a new request.\
Requesters get notified when a reviewer triages their request. Each of these\
has its own setting, and you can only enable or disable them through the API; neither is available on the account notifications page in the UI.

Snyk batches these emails and sends them every three hours if there is new\
activity. You cannot change this frequency. To receive a notification, you\
must be a member of the Organization.

#### Auto-approve ignores <a href="#auto-approve-ignores" id="auto-approve-ignores"></a>

To ensure AppSec teams have the option to move as quickly as they do today, there is a setting to allow users with the reviewer permissions to automatically approve ignores they themselves create, which bypasses the need for triage.

#### Audit <a href="#audit" id="audit"></a>

You can export all ignore request data for your Organization from the past 90 days\
through the audit logs API only, in JSON format. Most customers use this\
to automate exports into their reporting tools and dashboards. After 90 days,\
Snyk no longer makes the ignore request data available.

### Review Ignore Request in the Snyk UI

Reviewers get email notifications about new requests pending their approval. You can review the request in the **Ignore Requests** page in Snyk Web UI.

1. Log in to the Snyk Web UI and select your [Group and Organization](https://docs.snyk.io/snyk-platform-administration/groups-and-organizations).
2. Navigate to **Organization** > **Ignore requests**.

You can list all ignore requests in a **Pending**, **Approved**, or **Rejected** state on the **Ignore requests** page.

3. Choose an Ignore request and then select **Manage** to view the details.
4. Investigate the potential risk and decide whether you need to approve or reject the request. You can change the ignore type and expiration prior to approving.
5. Add a comment to explain the decision. Requesters and reviewers cannot go\
   back and forth in comments; use this field to summarize any offline\
   discussion before you approve or reject.

{% hint style="info" %}
Snyk does not support assigning specific reviewers to ignore triage requests. Any user with reviewer permission can pick up any pending request
{% endhint %}

The developer who submitted the request receives an email notification with the decision. The request is no longer pending, and new tests will reflect the decision: either a finding that needs to be fixed if the request was rejected, or an ignored finding that is not shown by default.

### View pending ignore requests on the Issues page

When Ignore Approval Workflow is enabled for your Organization, the **Issues** page for a Project shows which findings have an ignore request awaiting approval. Any user who can view the issue sees this status. You do not need the reviewer permission.

* A finding with a request awaiting approval shows a **Pending Ignore Request** status on the issue card and in the issue details. The status is separate from the **Ignored** status.
* Snyk removes the **Request to Ignore** action from the finding.
* The **STATUS** filter includes a **Pending Ignore Request** check box with a count of the findings that have a request awaiting approval. You can combine it with the other filters.

After a reviewer approves the request, the finding shows as ignored. After a reviewer rejects the request, the finding returns to open and you can request an ignore again.

{% hint style="info" %}
Run a new test after you submit a request to see the pending status. Snyk does not update the status immediately.
{% endhint %}

When Ignore Approval Workflow is disabled, the **Pending Ignore Request** check box is disabled and shows a count of 0. Organizations that ignore findings directly, without an approval step, see no other change.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/ignore-issues/ignore-approval-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.