Skip to content
Cómo hacer Admin

Deleting your organization

Deleting your organization

This article explains how to remove an entire Dailybot organization — not just your personal login. Deleting an org affects every member, connected chat workspace, and historical data tied to that org.

Before you begin

  • Personal account vs org: Closing your own account removes you from Dailybot; it does not automatically delete the whole company workspace if other admins remain. Deleting the organization removes the shared workspace and its data for everyone, subject to product and legal retention rules.
  • Permissions: You must be able to perform org-level destructive actions — often the sole Organization admin or you must transfer admin to yourself after coordinating with stakeholders.
  • Billing: Resolve open invoices or subscription cancellation with your finance owner so you are not surprised by a final charge cycle.
  • Backups and exports: Export anything your compliance or leadership requires before deletion. Deletion is intended to be irreversible for the org as a working environment.

Data consequences and irreversibility

After org deletion, members typically lose access to check-ins, kudos, Home feed history, and configuration for that org. Some records may be retained for a period for security, abuse prevention, or legal obligations, then purged or anonymized per Dailybot’s privacy and retention policies — see Data retention policies and Requesting data deletion. Do not treat deletion as a substitute for a formal data subject request if you need a documented GDPR process.

Warning: Once the org is deleted, you cannot “undo” it through the UI. You would need to create a new org and reconnect integrations from scratch.

Steps

  1. Sign in as an org admin and open Organization or Settings in the web app.
  2. Confirm you are deleting the correct org if you belong to more than one (switch workspace first if the product uses a workspace picker).
  3. Remove or reassign dependency: note active billing, custom integrations, and scheduled workflows so stakeholders know they will stop.
  4. Transfer admin if required: if policy demands more than one approver, coordinate with the other Organization admin(s) before proceeding.
  5. Open Delete organization, Close workspace, or the equivalent danger-zone action (exact label varies by version).
  6. Read the on-screen summary of what will be removed and any retention caveats.
  7. Type the organization name or confirmation phrase if prompted — this prevents accidental clicks.
  8. Confirm deletion and wait for a success message or email receipt if the product sends one.
  9. Ask a colleague to try logging in: they should no longer access the deleted org.
  10. If you only meant to leave yourself, use Close account instead of deleting the whole org.

What to expect after

The workspace stops accepting new activity from chat and the web app for that org. Members may see errors or empty state if they still have old links. For questions about residual data, use Requesting data deletion or contact support with your org identifier from billing or past emails.