> 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/zh/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).

# 批准促销代码监控违规

<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">参加 PXA 课程</a>

当违规的所有必需工作都完成后，您可以批准该违规以完成并关闭它。

1. 从左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-db1131f1b95ffbfa026aac99b07a7ffe0564b3b6%2F477fa23d9ffe966a6d1191fbd504e9a68f4c3918efe5cee5cb7bbd826e591fea.svg?alt=media) **\[保护]** → **违规**.
2. 在……上 *违规* 在屏幕上，将鼠标悬停在要批准的违规上并选择 **编辑**.
3. 在……旁边 *违规信息*，找到 **状态** 下拉菜单并选择 **已批准**.
   * 请参见 *状态参考表* 以获取更多信息。
4. 选择 **保存违规** 以保存你的更改。
   * 一旦违规被批准并保存，将向合作伙伴发送电子邮件和平台通知，告知其批准结果。

#### 状态参考

| 状态   | 说明                                             |
| ---- | ---------------------------------------------- |
| 新建   | 此状态适用于尚未采取任何行动的新违规。                            |
| 进行中  | 此状态表示违规正在审核中，处理方案仍在确定。                         |
| 阻塞   | 此状态适用于已审核且在决定下一步之前仍需更多信息的违规。                   |
| 已完成  | 此违规的处理流程已完成。                                   |
| 已批准  | 此状态适用于已被认定违反政策协议的违规。将向合作伙伴发送电子邮件和平台通知，告知其违规情况。 |
| 质量保证 | 此状态适用于已审核且正在由组织内第二个人员复审的违规。                    |
| 已拒绝  | 此状态适用于未被发现违反政策条款或协议的违规。                        |
| 无效   | 此状态适用于缺乏依据、真实性不足或结论不明确的违规。                     |
| 复制   | 此状态适用于重复违规或您以前处理过的违规。                          |


---

# 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://help.impact.com/brand/zh/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=<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.