> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/promo-code-monitoring/approve-a-promo-code-monitoring-violation.md).

# Approve a Promo Code Monitoring Violation

<a href="https://pxa.impact.com/student/activity/1117601?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=pro-350&#x26;utm_campaign=help-center" class="button primary">Take the PXA course</a>

Once all of the required work for a violation is complete, you can approve the violation to finish and close it out.

1. From the left navigation menu, select ![](/files/R8AxmtABBX7EqHjIMAwy) **\[Protect]** → **Violations**.
2. On the *Violations* screen, hover over the violation you want to approve and select **Edit**.
3. Next to *Violation Information*, find the **Status** dropdown and select **Approved**.
   * See the *Status reference table* below for more information.
4. Select **Save Violation** to save your changes.
   * Once the violation is approved and saved, an email and platform notification will be sent to the partner informing them of the approval.

#### Status reference

| Status            | Description                                                                                                                                                                       |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| New               | This status is for new violations where no action has been taken yet.                                                                                                             |
| In Progress       | This status indicates that a violation is in review and a course of action is still being decided.                                                                                |
| Blocked           | This status refers to violations that have been reviewed and are waiting for more information before any next steps can be decided upon.                                          |
| Completed         | The process of this violation has been completed.                                                                                                                                 |
| Approved          | This status is for violations that have been found to break the policy agreement. An email and platform notification will be sent to the partner informing them of the violation. |
| Quality Assurance | This status is for violations that have been reviewed and are in the process of being reviewed by a second person within the organization.                                        |
| Rejected          | This status is for violations that have not been found to break policy terms or agreements.                                                                                       |
| Invalid           | This status is for violations that are not well-founded, authentic, or conclusive.                                                                                                |
| Duplicate         | This status is for repeat violations or violations you have dealt with before.                                                                                                    |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/promo-code-monitoring/approve-a-promo-code-monitoring-violation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
