Remove or deactivate a user
Remove permanently frees the seat; Deactivate locks them out but keeps the seat. Both audited. Personal accounts stay for other workspaces.
Written By Salvatore Sinigaglia
Last updated About 5 hours ago
Remove permanently frees the seat; Deactivate locks them out but keeps the seat. Both audited. Personal accounts stay for other workspaces.
Remove or deactivate a user
Two flavors of offboarding: Remove = full removal from this workspace, seat freed (if user has no other memberships in your Org). Deactivate = user keeps account but cannot log in until reactivated, seat still counted. Both at Settings → Team → People → action menu.
Who is this for
Admins handling team changes: someone leaves the company, a contractor's project ends, a member needs temporary suspension during an investigation.
Remove vs Deactivate — when to use which
Remove is the most common. Deactivate is reserved for cases where the membership might be restored.
How to remove a member
Step 1: Open People page
Navigate to Settings → Team → People.
Step 2: Find the user
Search by name or email, or scroll the table.
Step 3: Action menu → Remove from workspace
Click the three-dot icon → Remove from workspace.
Step 4: Confirm
A confirmation dialog shows:
- Member's name + email
- What loses access: this workspace's data and settings
- What's preserved: their personal account (if they have other workspace memberships)
There is no "also revoke their API keys" checkbox — removing a member does not automatically revoke their API keys. Revoke those separately (see team-112).
Click Confirm removal. The member is soft-deleted from the team and disappears from your People page immediately.
Step 5: Audit log entry
The removal is recorded in the audit log with action member.remove (target = the removed user).
How to deactivate a user
Same flow, but pick Deactivate instead of Remove. Effect:
- User cannot log in
- User retains their membership (not removed)
- Seat is still counted (deactivation doesn't free seats)
- The change is recorded in the audit log with action
member.status-change
Reactivate
Find them in the People list (toggle "Show deactivated" if hidden) → action menu → Reactivate. Sessions are not restored — they log in fresh. Same role, same workspace memberships, same data access.
Seat accounting on removal
To free a seat occupied by a now-irrelevant user: remove them from all workspaces in your Org.
What happens to their stuff
When you remove or deactivate a user:
This is intentional: removing a teammate shouldn't break running automation or lose attribution history.
Cannot remove
You cannot remove:
- Yourself from your own workspace (must transfer ownership first or have another admin remove you — see team-105)
- The only owner of a workspace (must transfer ownership first)
- A user whose role you can't see/manage (you lack required permission)
Bulk removal
People page supports multi-select. Tick rows → toolbar → Remove from workspace → confirm. All removed in a single transaction (atomic — all or nothing).
Useful for end-of-project contractor offboarding or post-acquisition cleanup.
What you'll see
After removing:
- The row disappears from the People table (or shows Deactivated badge if you deactivated)
- Seat counter at
/settings/team/billingupdates (if seat freed) - Toast: "[name] removed from workspace"
- Audit log entry visible in
/settings/team/audit-log
Common issues
- "Cannot remove last owner": transfer ownership first.
- "You can't remove yourself": ask another admin, or transfer ownership and let them remove you.
- Seat counter didn't decrease after removal: user has another membership in your Org. Remove from all to free.
- Removed user's API keys still calling our API: removal doesn't auto-revoke keys. Revoke them from Settings → Team → API Keys before or after offboarding (see team-112); contact support if you need help.
- Deactivated user can still log in: allow a short delay for the session to expire, or contact support to force-invalidate.
- Removed by accident: re-invite via email. Their old data attribution survives, but you'll need to re-set role.
Soft delete + GDPR
Removal is soft delete (deleted_at timestamp). Audit + history retained. For permanent personal data erasure (GDPR right to be forgotten), the user (or you on their behalf with consent) must request personal account deletion — see acc-117 account deletion.
FAQ
What's the difference between Remove and Deactivate in Wevion?
Removing a user fully removes them from the workspace and frees the seat if they have no other memberships in your Org, while deactivating locks them out but keeps their account and still counts the seat. Both actions live at Settings → Team → People and are recorded in Wevion's audit log.
Does removing a user free up their seat?
Removing a user frees the seat only if they belong to no other workspace in your Org. If they're still a member of another workspace in the same Org, the seat stays counted. To free a seat for a dormant user, remove them from all workspaces. Deactivation never frees a seat.
What happens to campaigns and rules a removed user created?
They keep running. In Wevion, campaigns a removed user created stay in the workspace with ownership reattributed to system/admin, and their rules continue firing under the stored creator config. This is intentional so offboarding a teammate doesn't break running automation or lose attribution history.
Can I remove myself or the only workspace owner?
No. Wevion blocks removing yourself from your own workspace and removing the only owner — you must transfer ownership first (see team-105). You also can't remove a user whose role you lack permission to manage. To leave, transfer ownership or have another admin remove you.
FAQ
What's the difference between Remove and Deactivate in Wevion?
Removing a user fully removes them from the workspace and frees the seat if they have no other memberships in your Org, while deactivating locks them out but keeps their account and still counts the seat. Both actions live at Settings → Team → People and are recorded in Wevion's audit log.
Does removing a user free up their seat?
Removing a user frees the seat only if they belong to no other workspace in your Org. If they're still a member of another workspace in the same Org, the seat stays counted. To free a seat for a dormant user, remove them from all workspaces. Deactivation never frees a seat.
What happens to campaigns and rules a removed user created?
They keep running. In Wevion, campaigns a removed user created stay in the workspace with ownership reattributed to system/admin, and their rules continue firing under the stored creator config. This is intentional so offboarding a teammate doesn't break running automation or lose attribution history.
Can I remove myself or the only workspace owner?
No. Wevion blocks removing yourself from your own workspace and removing the only owner — you must transfer ownership first (see team-105). You also can't remove a user whose role you lack permission to manage. To leave, transfer ownership or have another admin remove you.
Steps
- Navigate to Settings → Team → People.
- Search by name or email, or scroll the table.
- Click the three-dot icon → Remove from workspace.
- A confirmation dialog shows: Member's name + email What loses access: this workspace's data and settings What's preserved: their personal account (if they have other workspace memberships) There is no "also revoke their API keys" checkbox — removing a member does not automatically revoke their API keys. Revoke those separately (see team-112). Click Confirm removal. The member is soft-deleted from the team and disappears from your People page immediately.
- The removal is recorded in the audit log with action member.remove (target = the removed user).
Last updated: 2026-05-17