> For the complete documentation index, see [llms.txt](https://docs.cortex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.io/ingesting-data-into-cortex/entities-overview/entities/archiving-entities.md).

# Archiving entities

## Overview

Archiving an entity in Cortex hides it from view without losing any of its history or data, so you can always restore it later. Entities can be [archived manually](/ingesting-data-into-cortex/entities-overview/entities/archiving-entities/archiving-entities-manually.md) (one at a time or in bulk) or [automatically](/ingesting-data-into-cortex/entities-overview/entities/archiving-entities/auto-archive.md) when Cortex no longer detects them in your integrations or their YAML file is deleted. All changes are recorded in your audit log.

Auto-archival applies to entities that are no longer backed by any discovery provider (e.g., Git, Kubernetes, your cloud account). If one reappears, it's unarchived automatically. Entities that failed to sync due to errors are skipped, so a temporary integration issue won't cause anything to disappear. Admins can disable this behavior to manage archiving manually instead.

Monorepo entities are handled separately via a feature flag. When enabled, they're included in auto-archival using partial key matching; when disabled, they must be archived manually.

Archived entities are not included in the following Cortex features:

* Scorecards and Initiatives
* Reports
* Eng Intelligence
* Cortex Query Language (CQL) features, including CQL reports and query builder
* Relationship graphs
* Workflows

{% hint style="info" %}
Cortex tags detected changes to signify whether an entity or repository has been archived. Learn more in [Viewing discovered entities](/ingesting-data-into-cortex/entities-overview/entities/discovery-audit.md).
{% endhint %}

## Displaying archived entities in Cortex

### Displaying archived entities in the Entities list

By default, archived entities do not appear in the **All entities** list, but you can choose to include them in your view.

{% hint style="warning" %}
This setting resets when you leave the page, so you'll need to toggle it on it each time you want to view archived entities.
{% endhint %}

**To include archived entities**:

1. From the main sidebar, expand **Catalogs**, then select **All entities.**
2. At the top of the list, click **Display**.<br>

   <div align="left" data-with-frame="true"><figure><img src="/files/wOrInpSpB5jFm4lMGcnO" alt="The &#x27;Show archived&#x27; toggle turned on to include archived entities in the list." width="563"><figcaption></figcaption></figure></div>
3. Toggle on **Show archived**.

### Displaying an Archived label next to an entity

The **Overview** section on an [entity's details page](/ingesting-data-into-cortex/entities-overview/entities/details.md) only shows active dependencies, child entities, and parent entities; anything archived is hidden. If the entity itself is archived, an **Archived** label appears next to its name:

<div align="left" data-with-frame="true"><figure><img src="/files/wyywXnofEAqlexU2x2v7" alt="An archived entity has an &#x27;Archived&#x27; label next to its name." width="563"><figcaption></figcaption></figure></div>


---

# 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.cortex.io/ingesting-data-into-cortex/entities-overview/entities/archiving-entities.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.