> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/library-packs/applications/genesys-troubleshooting/configuration-guide-genesys-troubleshooting.md).

# Configuration guide: Genesys troubleshooting

{% hint style="warning" %}
The configuration options on this page are only accessible to [administrators](https://docs.nexthink.com/platform/user-guide/administration/account-management/roles#roles-administration).

Refer to the [Usage guide: Genesys troubleshooting](/library-packs/applications/genesys-troubleshooting/usage-guide-genesys-troubleshooting.md) to use library content as a standard user.
{% endhint %}

## **Prerequisites** <a href="#documentation-pre-requisites" id="documentation-pre-requisites"></a>

This library pack contains content from the following required [expansion products](https://docs.nexthink.com/platform/overview/products):

* [Application Experience](https://docs.nexthink.com/platform/overview/products)

{% hint style="info" %}
The content in this library pack does not require an Application Experience license.
{% endhint %}

## **Included content and dependencies** <a href="#documentation-contentanddependencies" id="documentation-contentanddependencies"></a>

This library pack contains the following content and dependencies:

<table><thead><tr><th width="174">Content type</th><th width="171">Name</th><th width="238">Description</th><th>Dependencies</th></tr></thead><tbody><tr><td>​<a href="https://nexthink.gitbook.io/opd/user-guide/applications/managing-applications">Applications</a>​</td><td><strong>Genesys</strong></td><td>Desktop application covering the Genesys binaries</td><td>none</td></tr><tr><td>​<a href="https://nexthink.gitbook.io/opd/user-guide/applications/managing-applications">Applications</a></td><td>Genesys network</td><td>Network application covering Genesys specific destination network domains</td><td>none</td></tr></tbody></table>

### **Configuring "Genesys troubleshooting" pack** <a href="#documentation-configurationguide" id="documentation-configurationguide"></a>

Adapt these suggested configuration steps to edit and customize content according to your organizational needs.

### **Step 1 - Configure application**

1. From the main menu, navigate to the **Applications** > [Manage applications](https://docs.nexthink.com/platform/user-guide/applications/managing-applications) page.
2. Edit your application.
3. Applications are ready to use immediately after installation from the Library. Make any necessary adjustments if required. The list of binaries can be adjusted to the needs, and there is a checkbox configuration for changing the dashboard focus from device-centric to user-centric if needed.

***

RELATED TOPICS

* [Overview page: Genesys troubleshooting](/library-packs/applications/genesys-troubleshooting.md)
* [Usage guide: Genesys troubleshooting](/library-packs/applications/genesys-troubleshooting/usage-guide-genesys-troubleshooting.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 by asking a question.

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

```
GET https://docs.nexthink.com/library-packs/applications/genesys-troubleshooting/configuration-guide-genesys-troubleshooting.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.