> 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/rdm/knowledge-base/knowledge-base-articles/data-report.md).

# Data report

Configure a Data Report entry in Remote Desktop Manager to let users run SQL queries and generate reports without direct server access.

The ***Data Report*** session type can be used to empower any/all users to generate reports, without having to grant them access to the actual server.

## Settings

### General

Create a Data Report entry and define the connection string by either:

* Specify the connection in the entry itself.
* Use a credential entry.
* Inherited from a parent.
* Prompt for credentials.

### Parameters

Specify the parameters by setting the name, type and default value of all parameters.

### Query

Enter the query in the Query tab, which features an SQL syntax-highlighted text box with line numbers.

{% hint style="info" %}
Ensure that your DBA sets the proper user groups, and that each specific user(s) has access to it.
{% endhint %}


---

# 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://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/data-report.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 `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.