> 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/entry-settings/report-custom.md).

# Report (custom)

Configure Report (custom) entries in Remote Desktop Manager, including the report type, the PowerShell or linked script source, the timeout, and parameters.

This article details the many settings and options available for ***Report (custom)*** tool entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Type</strong></td><td><p>The kind of report the script produces. Select one of:</p><ul><li><strong>Connection list</strong></li><li><strong>Custom field report</strong></li></ul></td></tr><tr><td><strong>Script source</strong></td><td><p>Where the report script comes from. Select one of:</p><ul><li><strong>PowerShell</strong></li><li><strong>Linked entry</strong></li></ul><p>With <em><strong>PowerShell</strong></em>, the script is typed in the <em><strong>Script</strong></em> tab.</p></td></tr><tr><td><strong>Linked entry</strong></td><td>The entry that holds the script, chosen among the PowerShell session entries and the PowerShell script tools of the vault. Visible and required when <em><strong>Script source</strong></em> is set to <em><strong>Linked entry</strong></em>.</td></tr><tr><td><strong>Timeout (ms)</strong></td><td>The time allowed for the report script, in milliseconds, from 0 to 60000.</td></tr><tr><td><strong>Fields</strong></td><td>The columns of the report, one per line. Visible when <em><strong>Type</strong></em> is set to <em><strong>Custom field report</strong></em>.</td></tr></tbody></table>

### Script

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Script</strong></td><td>The PowerShell script that builds the report. On Windows, the <em><strong>Edit embedded script</strong></em> button opens the script in a separate editor. This tab is visible when <em><strong>Script source</strong></em> is set to <em><strong>PowerShell</strong></em>.</td></tr><tr><td><strong>Example</strong></td><td>A read-only sample script for the selected <em><strong>Type</strong></em>.</td></tr></tbody></table>

### Parameters

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Parameter name</strong></td><td>The label of the parameter. Click the name to rename the parameter in a window. In the script, type <code>$PARAMETER1$</code> for the first parameter, <code>$PARAMETER2$</code> for the second, and so on, as the example below the list shows.</td></tr><tr><td><strong>#</strong></td><td>The number of the parameter.</td></tr><tr><td><strong>Type</strong></td><td><p>The kind of value the parameter holds. Select one of:</p><ul><li><strong>Unused</strong></li><li><strong>Text</strong></li><li><strong>Secured</strong></li><li><strong>Env. variable</strong></li></ul></td></tr><tr><td><strong>Default value</strong></td><td>The value of the parameter. The value of a <em><strong>Secured</strong></em> parameter is masked.</td></tr><tr><td><strong>Add</strong></td><td>Add a parameter row at the end of the list.</td></tr><tr><td><strong>Delete</strong></td><td><p>Remove the last parameter row added with <em><strong>Add</strong></em>. The first five parameter rows cannot be removed. The delete button at the end of a row clears that parameter and sets its type to <em><strong>Unused</strong></em>.</p><p>On Linux, parameter names are edited directly in the list, the <em><strong>Add parameter</strong></em> button below the list adds a parameter, and the delete button of a row removes it.</p></td></tr><tr><td><strong>Prompt for parameters on open</strong></td><td>Prompt for the parameter values when the report runs.</td></tr></tbody></table>


---

# 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/entry-settings/report-custom.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.
