> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/ko/organization-settings/manage-your-admin-page-settings/delete-an-organization.md).

# 조직 삭제

조직을 삭제하는 방법을 알아보세요

조직이 실수로 생성되었거나 더 이상 필요하지 않은 경우 삭제할 수 있습니다. 그러나, [모든 장치는 조직에서 삭제되어야 합니다](/verkada-cameras/ko/configuration/view-and-edit-camera-settings/delete-a-camera.md)그리고 [모든 사용자는 조직에서 제거되어야 합니다](/command/ko/users-and-permissions/manage-users-in-your-organization.md) 조직을 삭제하기 전에.

{% stepper %}
{% step %}
**Verkada Command에서 All Products > Admin으로 이동합니다.**
{% endstep %}

{% step %}
**왼쪽 탐색 메뉴에서 General을 선택합니다.**
{% endstep %}

{% step %}
**Organization Details 아래에서 Delete Organization을 선택합니다.**
{% endstep %}
{% endstepper %}


---

# 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://help.verkada.com/command/ko/organization-settings/manage-your-admin-page-settings/delete-an-organization.md?ask=<question>&goal=<user_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.