Skip to content
Troubleshooting Admin

All members in my org were automatically deactivated

All members in my org were automatically deactivated

Suddenly every member in your organization shows as deactivated, or people report they cannot access Dailybot even though you did not remove them. This can match a known incident class (tracked internally as CORE-1526): an automated job or sync incorrectly flips member status org-wide.

Quick check

  • Confirm scope — Is it literally all members, or only a team or integration-linked subset?
  • Check admin audit — Note any recent changes to billing, SSO, or directory sync before the event.
  • Do not panic-delete the org — Mass deactivation is usually reversible; avoid destructive steps until support confirms.
  • Preserve billing context — Capture current plan and invoice contact in case support needs to correlate timing.
  • Open a high-priority ticket — Reference CORE-1526 if support asks for the internal ID.

Common causes and fixes

Known issue: incorrect bulk deactivation (CORE-1526)

Under specific conditions, a backend process has deactivated large sets of members by mistake. The organization, billing, and chat integrations may still exist — only member active flags were wrong.

What to do: Contact Dailybot support immediately with your organization name, approximate time you noticed the issue, and whether anyone remains active (for example, the owner). We can bulk reactivate members after verifying your org on our side. Do not rely on each person re-inviting themselves unless support directs you to — that can complicate seat accounting.

Reactivation steps (typical)

  1. Org admin emails support or uses the priority channel your contract specifies.
  2. Support validates the org and runs a safe reactivation or instructs you to use an admin tool if available in your edition.
  3. Members sign in again through your chat platform if SSO or tokens expired during the outage.
  4. Review automations and agent workflows that skipped runs while users were inactive.

Prevention and monitoring

After recovery, watch member counts daily for a short period. Ensure directory sync rules (if you use them) only deactivate users who truly left the company. If your org uses SCIM or HR integrations, confirm deprovision rules are narrow.

We publish fixes for root causes in release notes; ask support whether your org was affected by a known patch window.

If none of this worked

Escalate with:

  • Organization ID or URL slug if you know it
  • List of a few affected emails (domains only if privacy policy requires)
  • Whether chat platform membership still looks correct

We prioritize org-wide lockouts.