> 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/social-monitoring/create-a-social-violation.md).
# 创建社交违规
{% hint style="info" icon="lock" %}
此功能仅适用于特定的 impact.com 版本或附加功能。联系我们以升级您的账户并获取访问权限！
{% endhint %}
1. 在左侧导航栏中，选择  **\[保护]** → **监控** → **社交**.
2. 在……上 *社交* 在屏幕上，将鼠标悬停在要为其创建违规记录的帖子上，然后选择  **\[更多]** → **创建违规事项**.
3. 查看 *社交* 和 *违规* 信息：
社交信息参考
| 字段 | 说明 |
| ------ | ------------- |
| 账号名 | 与该违规关联的社交账号名。 |
| 详情 | 该帖子的违规信息。 |
| 受影响的帖子 | 受影响帖子问题的明细。 |
违规信息参考
{% hint style="success" icon="memo" %}
**注意**：违规信息会根据社交审核自动填充，您可以编辑这些信息。
{% endhint %}
| 字段 | 说明 |
| ---- | ---------------------------------------------------------------------------------------------------------------------- |
| 问题 | 在特定社交账号名上发现的问题类型。 |
| 说明 | 问题类型的描述。若默认描述不足以说明，请使用此字段描述违规情况。 |
| 状态 | 使用下拉菜单指示违规状态。状态包括：
• 新建
• 进行中
• 已阻塞
• 已完成
• 已批准
• 已拒绝
• 无效
• 重复
|
| 严重程度 | 使用下拉菜单指示违规的严重程度——通常，越严重的违规表示应尽快解决。 |
| 到期日期 | 使用日历和时间下拉菜单指定违规解决的截止日期。 |
| 附件 | 如适用，请选择 **选择文件** （或拖放）与此违规相关的文件（例如违规本身的截图）。 |
| 备注 | 使用文本字段添加有关此违规的评论。当设置为 **公开**，所有相关方（即创作者、您以及其他账户成员）都可以看到它。当设置为 **私密**，只有您和您的其他账户成员（创作者除外）可以看到它。 |
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/social-monitoring/create-a-social-violation.md?ask=&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.