3 KiB
| stage | group | info | type |
|---|---|---|---|
| Manage | Access | To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers | reference, howto |
Abuse reports (CORE ONLY)
View and resolve abuse reports from GitLab users.
GitLab administrators can view and resolve abuse reports in the Admin Area.
Receiving notifications of abuse reports
To receive notifications of new abuse reports by e-mail, follow these steps:
- Select Admin Area > Settings > Reporting.
- Expand the Abuse reports section.
- Provide an email address.
The notification email address can also be set and retrieved using the API.
Reporting abuse
To find out more about reporting abuse, see abuse reports user documentation.
Resolving abuse reports
To access abuse reports, go to Admin Area > Abuse Reports.
There are 3 ways to resolve an abuse report, with a button for each method:
- Remove user & report. This:
- Deletes the reported user from the instance.
- Removes the abuse report from the list.
- Block user.
- Remove report. This:
- Removes the abuse report from the list.
- Removes access restrictions for the reported user.
The following is an example of the Abuse Reports page:
Blocking users
A blocked user cannot log in or access any repositories, but all of their data remains.
Blocking a user:
- Leaves them in the abuse report list.
- Changes the Block user button to a disabled Already blocked button.
The user is notified with the following message:
Your account has been blocked. If you believe this is in error, contact a staff member.
After blocking, you can still either:
- Remove the user and report if necessary.
- Remove the report.
The following is an example of a blocked user listed on the Abuse Reports page:
NOTE: Note: Users can be blocked and unblocked using the GitLab API.