> 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/create-new-device/asset-bulk-import.md).

# Bulk actions

This page describes the asset bulk actions in more detail

The functionality of **Asset Bulk Actions** allows managing the fleet by importing, editing, or deleting multiple assets at once. Asset bulk actions are managed in the **Asset Inventory**.

### Bulk import

Bulk import allows importing multiple assets at once to the **Asset Inventory**. Assets can be imported to an existing **Data Flow** or to an **Integration (no data processing (LoRa only))**. **HTTP,** **MQTT** **& CoAP** devices can also be bulk uploaded.

To import multiple assets at once, *+ Bulk import* has to be selected on the **Asset Inventory Overview**.

![Bulk import on the Asset Inventory Overview](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2F3sQz6seQBWB1c3MOI3wI%2Fscreely-1685009458877.png?alt=media\&token=97654315-4571-4d58-8706-442232d39174)

Data processing either to an existing **Data Flow** or to a **Connectivity integration** has to be defined. The CSV file needs to be uploaded accordingly. Find more details of how to use **CSV templates** [here](/device-management/create-new-device/bulk-import-csv-templates.md).

![](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2F6sRc9RyHYmxFT5MXQAO3%2Fscreely-1685032100465.png?alt=media\&token=c4f17fe9-6402-4be4-9f75-9a5eaa753551)

Once the CSV file is uploaded, the file validation can be started. If the validation is successful, the import can start. All imported assets will be displayed now on the **Asset Inventory Overview**.

If further assistance is required, please contact us at <support@akenza.io>

### Bulk edit

Bulk edit allows editing the common set of properties of the current selection of Assets. Single or multi-select of Assets is possible. Only one field can be edited at a time. Fields that have not been selected will not be changed.

Editable fields are supported for:

* Name
* Description
* LoRa properties
* Custom field values

Bulk edit is possible via filter or by selecting single device ID's.

### Bulk register & deregister

Bulk register allows registering multiple Assets at once. A Data Flow can be assigned and edited to a set of Assets.

{% hint style="info" %}
This will remove the Assets from the LNS and require a rejoin upon registration.
{% endhint %}

Bulk deregister allows deregistering multiple Assets at once. Deregistering is possible via filter or by selecting single device ID's.

### Bulk delete

Bulk delete allows deleting a set of Assets. Deleting is possible via filter or by selecting single device ID's.

{% hint style="info" %}
Optionally: Assets can be deleted on the LNS (LoRaWAN Network Server).
{% 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.akenza.io/device-management/create-new-device/asset-bulk-import.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.