> 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/halopsa.md).

# HaloPSA

Configure HaloPSA dashboard entries in Remote Desktop Manager, including the ticketing server URI, application identity, authentication mode, and page size.

This article details the many settings and options available for ***HaloPSA*** session entries in Remote Desktop Manager.

{% hint style="info" %}
When the data source supports system-level ticketing settings, the ***Ticketing server URI***, ***Application identity***, and ***User credentials*** lists are displayed. Each one selects whether its group of settings comes from the system settings (or ***My account*** for user credentials) or from the current entry. The fields of a group are displayed only when that group is set to ***Current session***, and a read-only ***Effective settings*** summary shows the values in effect.
{% endhint %}

<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><tr><td><strong>Display</strong></td><td>Select how the session is displayed when the entry is launched.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list.</td></tr></tbody></table>

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Ticketing server URI</strong></td><td><p>Select where the URL of the HaloPSA instance comes from. Displayed when the data source supports system-level ticketing settings:</p><ul><li><strong>System settings</strong></li><li><strong>Current session</strong></li></ul><p>When the URL is set in the entry, enter the URL of the HaloPSA instance. A valid HTTP or HTTPS URL is required. Click the <em><strong>Navigate URL</strong></em> button to open the URL in your web browser.</p></td></tr><tr><td><strong>Application identity</strong></td><td><p>Select where the authentication mode, client ID, client secret, and scope come from. Displayed when the data source supports system-level ticketing settings:</p><ul><li><strong>System settings</strong></li><li><strong>Current session</strong></li></ul></td></tr><tr><td><strong>Authentication mode</strong></td><td><p>Select how Remote Desktop Manager authenticates to HaloPSA:</p><ul><li><strong>Client credentials</strong></li><li><strong>Username and password</strong></li></ul></td></tr><tr><td><strong>Client ID</strong></td><td>The client ID of the HaloPSA API application. Required when the application identity is set in the entry.</td></tr><tr><td><strong>Client Secret</strong></td><td>The client secret of the HaloPSA API application. Displayed and required only when <em><strong>Authentication mode</strong></em> is set to <em><strong>Client credentials</strong></em>.</td></tr><tr><td><strong>Scope</strong></td><td>The scope requested from HaloPSA. The default is <code>all</code>, which is also used when the field is left empty.</td></tr><tr><td><strong>User credentials</strong></td><td><p>Select where the HaloPSA username and password come from. Displayed when the data source supports system-level ticketing settings and the authentication mode in effect is <em><strong>Username and password</strong></em>:</p><ul><li><strong>My account</strong></li><li><strong>Current session</strong></li></ul></td></tr><tr><td><strong>Username</strong></td><td>The username of the HaloPSA account. Displayed and required when the authentication mode in effect is <em><strong>Username and password</strong></em> and the user credentials are set in the entry.</td></tr><tr><td><strong>Password</strong></td><td>The password of the HaloPSA account. Displayed and required when the authentication mode in effect is <em><strong>Username and password</strong></em> and the user credentials are set in the entry.</td></tr><tr><td><strong>Page size</strong></td><td>Set the maximum number of tickets fetched at each refresh, from 50 to 200 in increments of 25. The default is 50.</td></tr><tr><td><strong>Effective settings</strong></td><td>A read-only summary of the ticketing server URI and application identity in effect for the entry, plus the user credentials when the authentication mode in effect is <em><strong>Username and password</strong></em>. Displayed when the data source supports system-level ticketing settings.</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/halopsa.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.
