> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/configuration/gui-behavior/hide-tray-icon.md).
# Hide tray icon
{% hint style="info" %}
This policy is applicable to version 2.0 and above
{% endhint %}
This policy controls if KONNEKT shows an icon in the window's start bar tray area.
If the policy is enabled, the tray icon is shown. If the policy is disabled, no tray icon is visible. Users can restart KONNEKT with the `/ui` option to have a tray icon.
{% hint style="warning" %}
To apply the policy you have to restart **KONNEKT**
{% endhint %}
### **Policy information:**
**Policy Name:** Tray Icon
### Registry
**Key names:** `ShowTrayIcon`\
**Key type:** REG\_DWORD (32-Bit Value)
## **There are several ways to apply the policy:**
* manually by adding the key in the registry under machine or user registry settings
* via GPO, see [settings via GPO](/configuration/management-options/settings-via-gpo.md)
* pushing policies via Intune, see [settings for Intune Managed Devices](/configuration/management-options/setting-for-intune-managed-devices-1/intune-gui-settings.md#tray-icon)
**Policies** stored in:
`HKEY_CURRENT_USER\SOFTWARE\Policies\GlueckKanja\Konnekt`
`HKEY_LOCAL_MACHINE\SOFTWARE\Policies\GlueckKanja\Konnekt`
---
# 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.konnekt.io/configuration/gui-behavior/hide-tray-icon.md?ask=&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.