docs/source/guide/support_reports.md
Support reports give you a safe, low-friction way to tell the HumanSignal team what’s happening inside your Label Studio Enterprise deployment.
These reports bundle together anonymized operational metrics and environment details that our support and product teams use to:
Go to Organization > Settings > Support Reports.
Under Reports, click Generate New Report.
The report status is displayed under reports and moves from Pending → Running → Completed.
For large organizations with lots of data, this may take several minutes.
Once completed, you can use the action icons to:
!!! note To download the ZIP file, you need to have persistent storage configured. This is because when generating a support report, Label Studio persists the report artifact using the configured storage backend before it becomes available for download.
If you do not have persistent storage configured, or if the credentials are not valid, you will receive an error when you try to download the ZIP file.
You can configure your settings so that all reports are automatically emailed to a designated email address.
Enter the email address that should receive the reports. Separate multiple email addresses with a comma.
You can do this automatically for each report that is generated by toggling the options on, or you can do it manually using the actions under the Reports section.
Support reports are designed to be useful for debugging and planning while remaining safe to share:
Operational metrics and usage patterns
For example:
Environment profile
High-level information about:
!!! info Tip
Because the report is just a ZIP file with a JSON document inside, you can open it locally, feed it to your internal tooling, or attach it directly to a ticket.
Support reports are intentionally conservative:
No raw task data or annotations
Reports never include label text, documents, images, audio, annotation payloads, or other labeling data.
No PII data:
No label text, images, audio, or user names. Only aggregated and anonymized statistics.
Configuration without secrets:
Environment details focus on what is enabled and how the system is configured, not on credentials, keys, or proprietary URLs.
You control what is shared:
If you need even stricter controls (for example, internal review and approval workflows before anything is shared), support reports are easy to plug into those processes because they are:
We recommend generating a support report when:
In many cases, attaching a fresh support report to your initial ticket lets us skip several diagnostic steps and go straight to suggested fixes and improvements.