> 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/system-settings/configure-konnekt-for-a-subset-of-users.md).

# Skip Account Wizard

{% hint style="info" %}
Available in KONNEKT 2.2.0 or newer
{% endhint %}

When KONNEKT starts, it automatically deploys KONNEKT for the current user including the setup of an account. With this policy, you can prevent this.

**Policy name:** `SkipAccountWizard`

| Policy Setting     | Behavior                                             |
| ------------------ | ---------------------------------------------------- |
| Disabled (Default) | KONNEKT shall be configured for the current user     |
| Enabled            | KONNEKT shall NOT be configured for the current user |

{% hint style="warning" %}
It is very important to populate this policy **prior** the first start of KONNEKT to be effective.
{% endhint %}

Please see also [here](/troubleshooting/subscribe-a-subset-of-users.md) for related information on this topic.

### **There are several ways to apply the policy**

1. Via GPO, see [settings via GPO](/configuration/management-options/settings-via-gpo.md)
2. Pushing policies via Intune, see [settings for Intune Managed Devices](/configuration/management-options/setting-for-intune-managed-devices-1.md)
3. Manually by adding the key in the registry

### Manual setting in the registry

{% hint style="info" %}
You do not need this if you use GPO or Intune management
{% endhint %}

* **Value name:** `SkipAccountWizard`
* **Value type:** `REG_DWORD`
* **Value data:** `0` or `1`
  * `0` = disabled
  * `1` = enabled
* **Value stored in:**
  * `HKEY_CURRENT_USER\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/system-settings/configure-konnekt-for-a-subset-of-users.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.