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

# Download Directory

The Download Directory is the path where KONNEKT saves files to, that the user wants to recover.

The typical use-case is, that an error happened during the transfer of a file to SharePoint Online. In this case KONNEKT will show an error in Windows File Explorer. One option for users is to "[export file to download folder](/troubleshooting/how-to-deal-with-error-s.md)".

You can find more about handling errors [here](/troubleshooting/access-token-issues/error-message-about-missing-token.md).

## Default location

The default location for the Download Directory is `%USERPROFILE%\Downloads`.

## Set by user

Users can change the location manually in the preferences dialog, as long as the policy is not set.

<figure><img src="https://2727108687-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8zLVuKYctMIUr68_fs%2Fuploads%2FHgrsaQZ2pMQVH6Pf9gze%2Fimage.png?alt=media&amp;token=2ade21d1-061e-4cc1-8a68-925085ef22ea" alt=""><figcaption></figcaption></figure>

## Policy

{% hint style="info" %}
This policy is available in KONNEKT 2.6.0 or newer
{% endhint %}

### **Definition**

**Policy name:** `Download Directory`

**Policy Group:** KONNEKT / System Settings

| Policy Setting | Behavior                                                                                                                                      |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Not configured | The user-setting/default is used.                                                                                                             |
| Enabled        | The Download Directory configured in the policy is used by KONNEKT. The user can not change the Download Directory via the preference dialog. |
| Disabled       | The user-setting/default is used.                                                                                                             |

### **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)

{% hint style="warning" %}
Make sure to use the most current [ADMX file](/configuration/management-options/settings-via-gpo.md#admx-file), that matches your KONNEKT version.
{% endhint %}


---

# 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/download-directory.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.