> 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/other/license-key-on-multi-user-environments.md).

# Set license key

## License Key Storage

KONNEKT searches for license keys in two registry keys:

`HKEY_CURRENT_USER\SOFTWARE\GlueckKanja\Konnekt\License` (REG SZ)

`HKEY_LOCAL_MACHINE\SOFTWARE\GlueckKanja\Konnekt\License` (REG SZ)

{% hint style="info" %}
If a license key is set at machine level (HKLM), it will supersede a license key at user level (HKCU).
{% endhint %}

## License Key Configuration

There are several options how you can configure the license key:

|         Option        |                                                              Description                                                             |                                                                          Use Case                                                                         | Lic Key Storage Location |
| :-------------------: | :----------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------: | :----------------------: |
| **Interactive Setup** |                                              Enter the key during the interactive setup                                              |                                                  This option may be a good choice for a singular system.                                                  |           HKLM           |
|       **Policy**      |                                             Set the license key via GPO or Intune policy.                                            | <p>This is the recommended approach for managed environments.<br>See <a href="#set-license-key-via-registry-gpo-mdm">Set License Key</a> for details.</p> |       HKLM or HKCU       |
|   **MSI Parameter**   | <p>Sets the license key as a MSI-parameter<br>(e.g. with silent <a href="/installation/setup.md#silent-installation">Setup</a>).</p> |                                    This option may be a good choice for environments with a software deployment system.                                   |           HKLM           |
|  **Preferences Menu** |                                            Enter the license key in the preferences menu.                                            |                                                   This option may be used for single user systems, only.                                                  |           HKCU           |

Entering the license key in the preferences menu:

![](https://2727108687-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8zLVuKYctMIUr68_fs%2Fuploads%2FL2e802WbrQAboIv8ZTZy%2F2022-08-02%2016_32_15-Window.png?alt=media\&token=ab470fd7-9747-4b0c-820c-80d8aeaec65d)

{% hint style="danger" %}
The preference menu sets the license for the current user (HKCU), only. Other users logging into the same machine would also have to set the license.

If a license key is configured at HKLM, settings via preferences menu are not effective. (see [Set License Key](#license-key-storage) for details).
{% endhint %}

## Set License Key via Registry/GPO/MDM

Key name: **License**\
Type: REG\_SZ (String Value).

Sets the license key.

We recommend to use our [ADMX template](/configuration/management-options/settings-via-gpo.md#admx-file) to configure this setting.

## **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-other-settings.md#set-license-key)

**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/other/license-key-on-multi-user-environments.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.