> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/managing-a-workspace/general-settings/device-setup-assistant.md).

# Device Setup Assistant

Upload the mapping file that pre-fills device names, tags, and custom fields during an on-site installation.

This section configures the **mapping file** used by the [Device Setup Assistant](/device-setup-assistant/device-setup-assistant.md) when devices in this workspace are set up on site.

Without a mapping file, an installer types every value by hand at the device. With one, they select or scan the device, choose a single value, and the remaining device name, [tags](/device-management/managing-a-workspace/tags.md), and [custom fields](/device-management/managing-a-workspace/custom-fields.md) are filled in from the file. On a large rollout that is the difference between a considered installation and a long afternoon of typing.

{% hint style="info" %}
The Device Setup Assistant is available on **Expert plans**. See [akenza.io/pricing](https://akenza.io/pricing) for what each tier includes.
{% endhint %}

## Uploading a mapping file

{% stepper %}
{% step %}

### Prepare the CSV

Build a CSV whose columns match the tags and custom fields defined in this workspace, and decide which custom field acts as the **primary field**, the one an installer picks from on site. The field name rules and a downloadable template are on the [Device Setup Assistant overview](/device-setup-assistant/device-setup-assistant.md).
{% endstep %}

{% step %}

### Upload it

Open **Device Setup Assistant** on the [General settings](/device-management/managing-a-workspace/general-settings.md) page and select *Upload file*. The section shows *No file uploaded* until a file is in place.
{% endstep %}

{% step %}

### Save

Select *Save settings*. The file now applies to installations in this workspace.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The custom fields and tags named in the CSV must already exist in the workspace, spelled exactly as they are in the file. Values for names that do not exist are not applied.
{% endhint %}

{% content-ref url="/pages/GHXcYnuq8FQFCM4YK8xC" %}
[Overview](/device-setup-assistant/device-setup-assistant.md)
{% endcontent-ref %}


---

# 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.akenza.io/device-management/managing-a-workspace/general-settings/device-setup-assistant.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.