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
- Open Admin → Users.
- Search by display name, phone, or email. Optionally filter by role or status.
- Click the user row to open the detail panel.
- Tap Suspend in the actions footer.
- Optionally provide a reason (up to 400 characters) — it's recorded with the suspension.
- Confirm.
The user's status flips to suspended instantly. Their next sign-in attempt is blocked at the auth boundary.
Restoring
- Filter the user list by Status: Suspended.
- Open the user → tap Reactivate.
- 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