---
title: Managing abuse reports
---
> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).
Users in roles granted with appropriate [permissions](#configuring-required-permissions-for-managing-abuse-reports) can [manage](#editing-abuse-reports) abuse reports in the **Abuse report** application. The application allows [viewing](#managingabusereports-object_details) details of certain types of objects while editing related abuse reports. [Managingabusereports-object\_details](#managingabusereports-object_details)
You can use statuses to mark the reports – the system offers the **New**, **Solved**, and **Rejected** abuse report status. The statuses are just for convenient marking of reports. Changing a status does not influence the reported content.
## Editing abuse reports
When you edit an abuse report, the following information is displayed:
| Property name | Description |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Title | Title of the abuse report. |
| URL | URL of the page from which the report was sent. Click it to get redirected to that page. |
| Culture | Website culture from which the report was sent. |
| Object type | Type of object that was the cause of the report. If blank, the report was sent from a page. |
| Object name | Code name of the object that was the cause of the report. |
| Reported by | Site user who submitted the report. |
| Reported when | Time when the report was submitted. |
| Site | Website from which the report was submitted. |
| Status | Abuse report status, the following are possible:
**New** – The report is new and has not been solved yet.
**Solved** – Necessary actions have already been taken.
**Rejected** – The report was not considered being a case of website abuse. |
| Comment | Comment of the report entered by the reporting user. |
## Viewing object details
If you are editing an abuse report related to a blog comment, board message or forum post, the **Show object details** button is displayed.
Clicking the button opens a new window with details about the source of the report (the board message, blog comment or forum post). This functionality is ensured automatically by the web parts listed on the [Integrating abuse reporting with other community features](https://docs.kentico.com/k10/community-features/abuse-reports/integrating-abuse-reporting-with-other-community-features.md) page. You can also achieve it in transformations of these object types by using the **In-line abuse report** web part. See [Adding abuse reporting functionality to transformations](https://docs.kentico.com/k10/community-features/abuse-reports/adding-abuse-reporting-functionality-to-transformations.md) for more details.
## Configuring required permissions for managing abuse reports
Permissions for the Abuse report module can be set in the **Permissions** application:
1. Open the **Permissions** application.
2. In the first **Permissions for** drop-down list, choose **Module**.
3. In the second drop-down list, choose **Abuse report**.
You can grant the following permissions to the roles:
- **Read** – members of the role are allowed to view the abuse reports list.
- **Manage** – members of the role are allowed to edit, delete, mark as solved and reject abuse reports.