---
title: How to Change an Asset Schema
description: Change the schema assigned to an asset from the Configuration tab in Inspector.
---

[Skip to content](https://help.perspio.io/help/how-to-change-an-asset-schema#main-content)

English

Show submenu for translations

![Screenshot_3-4-2025_17232_](https://help.perspio.io/hs-fs/hubfs/Screenshot_3-4-2025_17232_.jpeg?width=200&height=53&name=Screenshot_3-4-2025_17232_.jpeg)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Contact us](mailto:servicedesk@perspio.io)

[Contact us](mailto:servicedesk@perspio.io)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [Perspio Help Centre](https://help.perspio.io/help?hsLang=en)
2. [Assets](https://help.perspio.io/help/assets?hsLang=en)
3. [Configuration](https://help.perspio.io/help/assets?hsLang=en#configuration)

# How to Change an Asset Schema

## Learn how to change an Asset Schema in Perspio. This step-by-step guide shows how to open an asset in Inspector, go to Configuration, enter edit mode, choose a new schema from the dropdown, and save the change.

#### Overview

An **Asset Schema** controls which Data and Snapshot are available for an Asset. Changing the schema is useful when an asset needs to follow a different configuration structure, such as when the asset type changes, the device setup changes, or the wrong schema was originally applied.

This article explains how to change an asset schema from **Inspector** and save the update.

---

#### Why this is important

Changing the schema ensures the asset is using the correct configuration layout.

This helps with:

- Showing the correct configuration fields for the asset
- Aligning the asset with the correct device or operational setup
- Improving data consistency across similar assets
- Avoiding confusion when users are editing or reviewing Asset Configuration

---

#### Before you start

Before changing the schema, confirm that:

- You have access to **Inspector**
- You have permission to edit **Asset Configuration**
- You know which schema should be applied
- Changing the schema will not remove or conflict with information your team still needs

---

#### Where to change the schema

The schema is changed from the asset record in:

**Inspector → Asset → Configuration**

---

#### How to change an asset schema

### Step 1 – Open Inspector

From the left-hand navigation, select **Inspector**.

Inspector is where you open and manage individual asset records.

![Click on Inspector](https://images.tango.us/workflows/1e04a135-1d6c-4162-81b2-48b0ac9369ca/steps/b702e3fa-530d-4886-a81e-2ee585961920/a3620182-007e-43e7-89f4-80e9e821f820.png?fm=png&crop=focalpoint&fit=crop&fp-x=0.0642&fp-y=0.1315&fp-z=2.6814&w=1200&border=2%2CF4F2F7&border-radius=8%2C8%2C8%2C8&border-radius-inner=8%2C8%2C8%2C8&mark-x=89&mark-y=212&m64=aHR0cHM6Ly9pbWFnZXMudGFuZ28udXMvc3RhdGljL2JsYW5rLnBuZz9tYXNrPWNvcm5lcnMmYm9yZGVyPTQlMkMyREE3NUUmdz0yMzUmaD04NiZmaXQ9Y3JvcCZjb3JuZXItcmFkaXVzPTEw)

 

---

### Step 2 – Open the asset

Locate and open the asset you want to update.

Use the asset list or search area to open the correct asset record before making changes.

![Click on 133…](https://images.tango.us/workflows/1e04a135-1d6c-4162-81b2-48b0ac9369ca/steps/c76e9e17-ec7e-4bfc-ac30-d3298b48c86a/28e4c704-b4b9-4661-b252-dcc4738ea812.png?fm=png&crop=focalpoint&fit=crop&fp-x=0.2115&fp-y=0.2390&fp-z=2.0600&w=1200&border=2%2CF4F2F7&border-radius=8%2C8%2C8%2C8&border-radius-inner=8%2C8%2C8%2C8&mark-x=63&mark-y=204&m64=aHR0cHM6Ly9pbWFnZXMudGFuZ28udXMvc3RhdGljL2JsYW5rLnBuZz9tYXNrPWNvcm5lcnMmYm9yZGVyPTQlMkMyREE3NUUmdz00NTgmaD01NSZmaXQ9Y3JvcCZjb3JuZXItcmFkaXVzPTEw)

 

---

### Step 3 – Open Configuration

Within the asset record, select **Configuration**.

The **Configuration** tab contains the asset’s configurable settings, including the schema currently assigned to that asset.

![Click on Configuration](https://images.tango.us/workflows/1e04a135-1d6c-4162-81b2-48b0ac9369ca/steps/baab9c85-b857-4d4a-91dd-ae546b496844/375c03a9-ec2e-42b8-a9b5-00c0ec110592.png?fm=png&crop=focalpoint&fit=crop&fp-x=0.0718&fp-y=0.5528&fp-z=2.5518&w=1200&border=2%2CF4F2F7&border-radius=8%2C8%2C8%2C8&border-radius-inner=8%2C8%2C8%2C8&mark-x=79&mark-y=317&m64=aHR0cHM6Ly9pbWFnZXMudGFuZ28udXMvc3RhdGljL2JsYW5rLnBuZz9tYXNrPWNvcm5lcnMmYm9yZGVyPTQlMkMyREE3NUUmdz0yODEmaD05MCZmaXQ9Y3JvcCZjb3JuZXItcmFkaXVzPTEw)

 

---

### Step 4 – Select Edit

Click **Edit** to enable changes.

#### Screen control: Edit

The **Edit** button places the Configuration screen into edit mode.  
Until Edit is selected, the fields are generally view-only.

 

![Click on Edit](https://images.tango.us/workflows/1e04a135-1d6c-4162-81b2-48b0ac9369ca/steps/cab66086-2a7c-4eca-8c6c-eb60c1f39d0c/0e53d36f-cfff-4f7b-b335-e51a253dd65f.png?fm=png&crop=focalpoint&fit=crop&fp-x=0.5184&fp-y=0.4882&fp-z=1.0278&w=1200&border=2%2CF4F2F7&border-radius=8%2C8%2C8%2C8&border-radius-inner=8%2C8%2C8%2C8&mark-x=1109&mark-y=103&m64=aHR0cHM6Ly9pbWFnZXMudGFuZ28udXMvc3RhdGljL2JsYW5rLnBuZz9tYXNrPWNvcm5lcnMmYm9yZGVyPTQlMkMyREE3NUUmdz00MCZoPTIzJmZpdD1jcm9wJmNvcm5lci1yYWRpdXM9MTA%3D)

 

---

### Step 5 – Select the new schema and save

In edit mode, locate the **Schema** field and choose the correct option from the dropdown list. Once selected, click **Save**.

#### Screen controls in this step

- **Schema dropdown**  
  This dropdown displays the schemas available for the asset. Use it to select the schema you want to apply.
- **Save**  
  The **Save** button applies the schema change to the asset. The new schema will become the active configuration structure for that asset.

### What this step does

This updates the asset so it uses a different configuration schema. After saving, the fields available in Asset Configuration may change depending on the schema selected.

![Select a Schema from the dropdown menu and press Save.](https://images.tango.us/workflows/1e04a135-1d6c-4162-81b2-48b0ac9369ca/steps/f9d90bdc-bfec-4604-897b-cfc0feb30477/576b991f-5637-4bc8-92da-c2d4d973170c.png?fm=png&crop=focalpoint&fit=crop&fp-x=0.6397&fp-y=0.3631&fp-z=2.2193&w=1200&border=2%2CF4F2F7&border-radius=8%2C8%2C8%2C8&border-radius-inner=8%2C8%2C8%2C8&mark-x=360&mark-y=339&m64=aHR0cHM6Ly9pbWFnZXMudGFuZ28udXMvc3RhdGljL2JsYW5rLnBuZz9tYXNrPWNvcm5lcnMmYm9yZGVyPTQlMkMyREE3NUUmdz00ODEmaD00NyZmaXQ9Y3JvcCZjb3JuZXItcmFkaXVzPTEw)

---

#### What to check after saving

After saving the new schema, confirm that:

- The correct schema is now shown on the asset
- The expected data fields are available
- The asset still matches the intended device or operational setup

If needed, review the rest of the Configuration tab to make sure all required fields are still correct after the schema change.

---

#### Best practices

- Only change the schema when you are confident the asset should use a different configuration structure
- Confirm the correct schema before saving
- Review the asset configuration after the change
- Use consistent schemas for similar asset types where possible

---

#### Troubleshooting

### I cannot edit the schema

Make sure you are in the **Configuration** tab and have clicked **Edit**.

### I do not see the schema I need

Check whether the schema exists in your tenant and whether it is available for that asset type.

### The fields changed after saving

This is expected. The schema controls which configuration fields are shown for the asset.

### I do not have access to change it

Your user role may not have permission to edit Asset Configuration. Contact your administrator if needed.

- [Introduction](https://help.perspio.io/help/introduction?hsLang=en#main-content)
  
  
  
  
  
    - [How to's](https://help.perspio.io/help/introduction?hsLang=en#how-tos)
- [Assets](https://help.perspio.io/help/assets?hsLang=en#main-content)
  
  
  
  
  
    - [Asset Inspector](https://help.perspio.io/help/assets?hsLang=en#asset-inspector)
    - [Utilisation Module](https://help.perspio.io/help/assets?hsLang=en#utilisation-module)
    - [Configuration](https://help.perspio.io/help/assets?hsLang=en#configuration)
    - [Events](https://help.perspio.io/help/assets?hsLang=en#events)
    - [Servicing](https://help.perspio.io/help/assets?hsLang=en#servicing)
    - [Asset Configuration](https://help.perspio.io/help/assets?hsLang=en#asset-configuration)
    - [Device Configuration](https://help.perspio.io/help/assets?hsLang=en#device-configuration)
- [Explorer](https://help.perspio.io/help/explorer?hsLang=en)
- [Dashboards](https://help.perspio.io/help/dashboards?hsLang=en#main-content)
  
  
  
  
  
    - [Configuration](https://help.perspio.io/help/dashboards?hsLang=en#configuration)
- [Reports](https://help.perspio.io/help/reports?hsLang=en#main-content)
  
  
  
  
  
    - [Available Reports](https://help.perspio.io/help/reports?hsLang=en#available-reports)
- [Groups](https://help.perspio.io/help/groups?hsLang=en#main-content)
  
  
  
  
  
    - [Security Groups](https://help.perspio.io/help/groups?hsLang=en#security-groups)
    - [Asset Groups](https://help.perspio.io/help/groups?hsLang=en#asset-groups)
- [Geofences](https://help.perspio.io/help/geofences?hsLang=en)
- [Workflows](https://help.perspio.io/help/workflows?hsLang=en)
- [Administration](https://help.perspio.io/help/administration?hsLang=en#main-content)
  
  
  
  
  
    - [Settings Module](https://help.perspio.io/help/administration?hsLang=en#settings-module)
    - [Admin Panel](https://help.perspio.io/help/administration?hsLang=en#admin-panel)
- [Devices](https://help.perspio.io/help/devices?hsLang=en#main-content)
  
  
  
  
  
    - [Troubleshooting](https://help.perspio.io/help/devices?hsLang=en#troubleshooting)
    - [Installation Guides](https://help.perspio.io/help/devices?hsLang=en#installation-guides)

[![](https://help.perspio.io/hs-fs/hubfs/Perspio%20Logo%20%E2%80%93%20Colour%20White%20%E2%80%93%20large%20%20RGB.png?width=786&height=177&name=Perspio%20Logo%20%E2%80%93%20Colour%20White%20%E2%80%93%20large%20%20RGB.png)](https://perspio.io)

2/50 Yeo St, Neutral Bay NSW 2089

[mailto:servicedesk@perspio.io](mailto:servicedesk@perspio.io) <https://www.facebook.com/InauroAus/> <https://www.inauro.io/>

Copyright © 2026 Inauro