> For the complete documentation index, see [llms.txt](https://docs.motar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motar.com/motar-core-services/intro-to-core-services/studio/deleting-and-archiving-listings.md).

# Deleting and Archiving Listings

To remove a listing, open the **Studio Listing** page and click the **trashcan icon** next to the edit button. 

<figure><img src="/files/1jp1Ups1qUnIVbqPLJOf" alt=""><figcaption></figcaption></figure>

A confirmation dialog will appear:

> *Are you sure you want to delete this listing?*

<figure><img src="/files/OxTUkNj7IYm4hKssdyy0" alt=""><figcaption></figcaption></figure>

#### Behavior of Deleted Listings

Deleted listings will:

* Be marked as **Archived** and set to *view only* in the listing tree.
* Remain available in any trainings where they are already in use.

#### Digital Thread Listings

If the listing is part of a **Digital Thread**, deletion from the Studio page is not allowed.&#x20;

Instead, you will be redirected to the Digital Thread section of the listing, where you can archive it by clicking the **trashcan icon**.

<figure><img src="/files/hDwBIlCllneSGZCoRVs2" alt=""><figcaption></figcaption></figure>


---

# 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.motar.com/motar-core-services/intro-to-core-services/studio/deleting-and-archiving-listings.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.