> For the complete documentation index, see [llms.txt](https://docs.qubitro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qubitro.com/platform/device/settings.md).

# Settings

## Device Settings

Update device details and manage metadata, tags, and unique IDs. Some settings may be restricted based on your role or integration type.

The **Device Settings** page allows you to update a device’s **general details**—such as its name, metadata, tags, and description—and provides unique identifiers for API interactions.

### How to Access Device Settings

{% stepper %}
{% step %}
**Go to the Device Detail Page**

Locate and select the device you want to configure.
{% endstep %}

{% step %}
**Select the Settings Tab**

In the top navigation (next to **Overview**), click **Settings**.
{% endstep %}
{% endstepper %}

### General

{% hint style="warning" %}
Some settings (e.g., **Delete Device**) may be **restricted** based on **your role** or **integration type**. If you require access, check your **permissions** or contact your project administrator.
{% endhint %}

#### Unique IDs

Used when interacting with the **Qubitro API** (read-only).

* **Device ID**: A unique identifier that may vary based on the data source. Some integrations (e.g., **cellular**) may display **SIM IDs**.
* **Device Token**: Used for authentication.
  * **MQTT**: Acts as the **password**.
  * **HTTP**: Used as the **Authorization** value in requests.

#### Metadata

Metadata allows manually adding non-dynamic information such as:

* **SKU Number**
* **Serial Number**
* **Customer Name**

{% hint style="success" %}
Metadata is automatically displayed on the Device Overview page and is accessible via API for programmatic use.
{% endhint %}

#### Tags

Organize and categorize your device for improved navigation and search.

* You can **assign up to three tags per device**.

{% hint style="warning" %}
If the tag limit is reached, you must remove an existing tag before adding a new one.
{% endhint %}

#### Device Avatar

Click the avatar to **upload a custom image** to visually distinguish your device.

#### Device Details

Customize device information:

* **Device Name** (max **32 characters**)
* **Device Brand** (max **32 characters**)
* **Device Model** (max **32 characters**)
* **Device Description** (max **32 characters**)

#### Created At

Displays the **exact date and time** when the device was added to Qubitro.

{% hint style="info" %}
The Created At date is displayed in the time zone selected in your account settings.
{% endhint %}

### Delete Device

Permanently remove the device and all associated data.

{% hint style="danger" %}
Deleting a device is irreversible and will **permanently** remove all data, including time series data, blob data (if any), functions, and widgets from dashboards that use this device’s data. Additionally, any associated resources like add-ons (e.g., storage views data) will **also** be deleted.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.qubitro.com/platform/device/settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.