> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/assets-archivieren.md).

# Archive assets

In eliona, assets cannot be permanently deleted. Instead, assets are archived.

Archived assets do disappear, but remain in the system in the background. Therefore, archived assets can be restored.

Archived assets cost no Infravolt.

## Why can't assets be deleted?

If assets could be permanently deleted, it would not be possible to trace completed tickets and tasks if they relate to the deleted asset.

## What happens when you archive an asset?

If you archive an asset, the following things happen:

* The asset no longer appears in the asset list
* The asset is no longer found when searching for it using the search function
* The asset appears in the asset archive
* Tickets and tasks related to the asset remain preserved, even if the tickets and tasks are already completed. The name or the GAI of the archived asset are not visible.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/aHhVxfut14lLD9MpA78X/51B5714F-3AF1-48B4-8D34-90BAF776F61D.png" alt=""><figcaption><p>Comparison: The same ticket before (A) and after (B) the corresponding asset was deleted.</p></figcaption></figure>

## Archiving an asset

{% @supademo/embed url="<https://app.supademo.com/demo/clm95pez541fov519o2ylufu4>" demoId="clm95pez541fov519o2ylufu4" fullWidth="true" %}

## Finding and searching archived assets

Archived assets are collected in the asset archive and can be viewed and searched there.

{% @supademo/embed url="<https://app.supademo.com/demo/cAqLRFazho_jmZyKo9R16>" demoId="cAqLRFazho\_jmZyKo9R16" fullWidth="true" %}

## Restoring archived assets

Archived assets can be restored from the asset archive.

{% @supademo/embed url="<https://app.supademo.com/demo/0iPydeJovg8aEJ-MW-mcg>" demoId="0iPydeJovg8aEJ-MW-mcg" fullWidth="true" %}


---

# 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.buildings.ability.abb/collection/english-v14/documentation/assets/assets-archivieren.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.