Trust & Safety

Pending Account Closures — Admin

How admins process or reject user self-deletion requests from the Pending Closures queue.

When a user submits a self-deletion request, it enters a 30-day holding queue. During this window admins can intervene — approving the closure early or rejecting it entirely.

Accessing the Queue

Navigate to Influenzic → Pending Closures. The list shows all users with a pending inzc_deletion_requested_at stamp, the date of request, and the days remaining in the grace period.

Processing Early

Click Process Now to immediately run the full closure cascade for a user without waiting for the 30-day period to expire. The steps are identical to the automatic cron processing:

  • User row tombstoned (email replaced with closed-{id}@account.invalid, display name anonymised, password randomised)
  • Social accounts, portfolio items, and portfolio media deleted
  • All inzc_* usermeta purged (except closure markers)

Rejecting a Request

Click Reject to cancel the closure request. The inzc_deletion_requested_at meta is removed and the user receives a notification informing them their request was declined. The account remains fully active.

The inzc_process_pending_closures daily cron also auto-processes any request older than 30 days. If you have not intervened by then, the closure proceeds automatically.

Was this article helpful?