> For the complete documentation index, see [llms.txt](https://docs.firecal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firecal.app/organizations/org-administration/delete-an-org.md).
# Delete an Org
Deleting an Org requires the **Admin** role, and it's permanent once it goes through, so CertLocker builds in time to change your mind.
{% hint style="warning" %}
**Read this first.** Deleting an Org permanently deletes its Departed Member Records and their documents, along with the Org's own content, like its training sessions and templates. Your Members keep their own Certs and Lockers; only their connection to your Org is removed. Export anything you need first.
{% endhint %}
## Open Delete Organization
Tap **Orgs** in the navigation bar, tap your **Org Card**, then tap the **Manage Icon** in the top right corner of the Org's profile, scroll to the bottom, and tap **Delete Organization**. The screen summarizes exactly what will be deleted and how the process works for your Org.
## Confirm by Name
Type your Org's name where it says **Type the org name to confirm**, then tap **Initiate deletion**. CertLocker asks once more. Tap **Initiate now**.
## What Happens Next
Your Members are notified, and a banner appears on the Org's profile showing when the deletion will happen. If your Org has more than one Admin, another Admin needs to confirm (with **Confirm or reject** on that banner). If you're the only Admin of an Org with other Members, they can **Dispute deletion** if they think it's a mistake. Until the deletion goes through, an Admin can stop it with **Cancel deletion**.
---
# 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.firecal.app/organizations/org-administration/delete-an-org.md?ask=&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.
