Skip to main content

Suspending and restoring users

For admins· 1 min read

Suspending blocks new sign-ins immediately. Existing JWT sessions stay valid until they expire — use Sign out everywhere for instant revocation.

The Suspend action on a user row blocks future sign-ins for that account. Use it for clear policy violations or compromise reports; for everything subtler, prefer Change role or a direct conversation.

Steps

  1. Open Admin → Users.
  2. Search by display name, phone, or email. Optionally filter by role or status.
  3. Click the user row to open the detail panel.
  4. Tap Suspend in the actions footer.
  5. Optionally provide a reason (up to 400 characters) — it's recorded with the suspension.
  6. Confirm.

The user's status flips to suspended instantly. Their next sign-in attempt is blocked at the auth boundary.

Restoring

  1. Filter the user list by Status: Suspended.
  2. Open the user → tap Reactivate.
  3. Optionally add a reason for the unsuspension. The original suspension reason and its timestamp are preserved in the audit log.

Limitations

  • Existing sessions stay valid until they expire. Suspending blocks new sign-ins; there is no force-sign-out button on the panel — suspension is the abuse path.
  • Suspension is an ops-tier action. The one hard guardrail is that you can't suspend yourself.

Common issues

  • The suspended user is still active in our analytics. Activity recorded before the suspension stays in metrics; that's the audit trail. Going-forward activity stops as their session expires.
  • Suspended user still active. They hold a session that pre-dates the suspension; it stops working as the session refreshes or expires.

Related

Did this answer your question? If not, email us and we'll improve this page.