> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/escalations/archive-escalation-policy.md).

# Archive escalation policy

You can archive an escalation policy when it's no longer associated with any integration. Visit your [escalations page](https://app.spike.sh/escalations), select a policy, click the settings icon, and select **Archive**.

<figure><img src="/files/oi0vV1nSihlG2WeU94Uq" alt="Archive option under escalation policy settings"><figcaption><p>Select Archive under the policy settings.</p></figcaption></figure>

## Restrictions

If the policy is in use on one or more integrations, archiving is not available. Update those integrations to use a different escalation policy first.

{% hint style="success" %}
Once the policy is no longer associated with any integration, you can archive it.
{% endhint %}

## FAQs

### Does archiving affect on-call schedules?

No. Archiving an escalation policy does not affect on-call schedules.

### Does archiving affect existing incidents?

No. Existing incidents retain a reference to the archived policy. Spike displays a notice on those incidents to flag that the policy has been archived.

### How do I restore an archived policy?

There's no self-serve restore option. Contact support via chat from the dashboard or email <support@spike.sh>.


---

# 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:

```
GET https://docs.spike.sh/escalations/archive-escalation-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
