> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/it/concepts/intermediate-concepts/reports.md).

# Report

I report in Devolutions Server riepilogano i dati di attività come accessi non riusciti, utilizzo delle password e consumo delle licenze per le revisioni di conformità.

I report in Devolutions Server forniscono viste riepilogative delle attività e della configurazione, così da poter rispondere rapidamente a domande operative e di conformità. Sono creati a partire dai dati di log e di audit e possono evidenziare elementi come accessi non riusciti, utilizzo delle password, consumo delle licenze o attività specifiche di un modulo.

Gli amministratori e gli auditor possono eseguire i report su richiesta o pianificarli, esportando i risultati quando necessario per una revisione esterna. Ad esempio, un team di sicurezza potrebbe generare un report mensile dei check-out degli account privilegiati e delle sessioni remote associate per soddisfare i requisiti di audit.

#### Argomenti correlati

* [Report](/server/it/web-interface/utilities/reports.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/server/it/concepts/intermediate-concepts/reports.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 `build a script that syncs our docs to a CMS` 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.