> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/help/workspace-and-organisation/model-archiving.md).

# Model Archiving

This article explains how **model archiving** works in Model Reef from a workspace perspective.

You will learn:

* What happens when you archive a model.
* How archiving differs from deleting.
* How to use archiving to manage model lifecycle and workspace clutter.

Archiving is a safe way to park models that are no longer active but still needed for reference or audit.

## 1. What it means to archive a model

When you archive a model:

* The model is moved from the active workspace view into an archive area.
* All contents are preserved, including:
  * Branches and variables.
  * Data Library entries.
  * Dashboards and reports.
  * Valuation settings.
  * Notes, comments, tags and attachments.
* The model stops appearing in normal active model lists and folders.

Archived models are still part of the workspace but are treated as inactive.

{% hint style="info" %}
Archiving preserves the complete model and its collaboration artefacts while removing it from active lists — it’s useful for keeping history without clutter.
{% endhint %}

## 2. Who can archive and restore models

Model archiving is controlled by permissions:

* Only **Owners** can archive or restore models.
* Editors and Viewers cannot archive models, even if they can see them.

This prevents accidental archiving of models that are still in use.

## 3. When to archive a model

You should consider archiving a model when:

* A project or transaction has completed.
* A financial year or planning cycle has closed and a new model has been created for the next period.
* A scenario or version is no longer used in day to day work but must be kept for record.
* You want to simplify the active workspace list for current work.

Archiving keeps history without cluttering the main workspace.

## 4. Restoring archived models

{% stepper %}
{% step %}

### Locate the archived model

Find the model in the archive area of the workspace.
{% endstep %}

{% step %}

### Restore it back into the active workspace

Restore the model to reactivate it.
{% endstep %}

{% step %}

### Place it in the appropriate folder if needed

Move the restored model into the correct folder or location in your active workspace.
{% endstep %}
{% endstepper %}

On restore:

* All previous permissions come back with the model.
* All data and collaboration artefacts are intact.

You can then continue working on the model, or use it as a base for new versions.

## 5. Archiving vs deleting

Archiving is **not** the same as deleting.

{% columns %}
{% column %}

#### Archiving

* Hides the model from active lists.
* Preserves all data and structure.
* Can be reversed at any time by restoring.
  {% endcolumn %}

{% column %}

#### Deleting

* Permanently removes the model from the workspace.
* Cannot be undone once confirmed.
* Should be used sparingly, usually only for test models or obvious duplicates.
  {% endcolumn %}
  {% endcolumns %}

{% hint style="danger" %}
Deleting is permanent and cannot be undone. Prefer archiving unless you are certain you will never need the model again.
{% endhint %}

***

## Related articles

* [Capex & Equipment Lifecycle Model](/use-cases/mining-energy-and-natural-resources/capex-and-equipment-lifecycle-model.md)
* [Build Scenario Aware Data Overrides](/how-tos/data-workflows-and-automation/build-scenario-aware-data-overrides.md)
* [What It Does (fundamentals only)](/help/stock-ticker-fundamentals/what-it-does-fundamentals-only.md)
* [Modifier Driver Fields](/syntax/drivers-syntax/modifier-driver-fields.md)