Trust & Safety

Ban & Account Suspension

How admins ban users, what cascades on ban, and how to lift a ban.

Admins can ban any brand or influencer account. A ban immediately blocks login and triggers role-appropriate cascades to protect other users.

Banning a User

Navigate to Influenzic → Users → Influencers (or Brands) and open the user detail. Click Ban User and enter a mandatory reason. The reason is:

  • Shown to the banned user on their next login attempt
  • Stored in inzc_ban_reason user_meta
  • Logged permanently in wp_inzc_ban_log alongside the acting admin’s ID and a timestamp

Appeal Blocking

Tick Block Appeal when banning to prevent the user from opening a support ticket to appeal the decision. This is appropriate for confirmed bad actors, fraudulent accounts, or users who have previously abused the appeal process.

Ban Cascades

User Role Cascade Effect
Brand Active campaigns → paused. Sent/viewed invitations → voided; escrowed funds refunded to brand wallet. Influencers on paused campaigns notified.
Influencer Pending/queued applications → withdrawn. Sent/viewed invitations targeting this influencer → voided; escrowed funds refunded to the brand.
In-flight projects are not automatically cancelled on ban. Brands/influencers on active projects when a counterpart is banned will see the project enter a stuck state. Use the dispute system or the admin project detail to cancel or resolve individual projects manually.

Lifting a Ban

Open the banned user’s detail and click Unban User. The ban is lifted immediately: inzc_is_banned and inzc_ban_reason meta are deleted, and the unban is logged in wp_inzc_ban_log. The user can log in immediately.

Note: previously voided invitations and withdrawn applications are not automatically restored. The user must re-apply or be re-invited.

Hooks: inzc_user_banned fires with ($user_id, $admin_id, $reason, $appeal_blocked). inzc_user_unbanned fires with ($user_id, $admin_id). Use these to sync ban status to external systems.

Was this article helpful?