Delete an organization

Use the owner-only danger zone, understand permanent deletion and account survival, and retry a failed deletion with the same organization ID.

By The SKaaS team. Last updated . Markdown version

Before deletion

Only an owner can delete an organization. Open Settings → Danger zone → Delete organization. The confirmation page says which organization will be removed. Type its exact short name to confirm.

Deletion permanently removes organization repositories, skills, releases, stored files, organization keys, memberships, integrations, settings and exported release manifests. This cannot be undone. User accounts, global personal keys, sessions and other organizations remain. A member who has no other organization still has an account.

Cancel an active, trialing or past-due paid subscription before deleting. The server refuses deletion while such a subscription remains. An ordinary member, service identity or restricted key cannot delete the organization.

Completion and retry

The page displays a receipt with the organization ID, completion time, document count and deleted file count. If deletion fails partway, retry the same confirmation page. It keeps the organization ID and typed short name even after membership was removed. Do not replace the organization ID with a slug. Repeating a completed deletion as the original owner returns the same receipt.

The API is POST /v1/organizations/{organization_id}/deletion, with { "confirm_slug": "acme" }. The ID comes from the signed-in organization's record. The raw authentication-library organization deletion route is disabled. A deletion receipt contains counts and identifiers, never skill content or secrets.