Deleting a user
This page only applies if each person on your team has their own 4admin login. If your firm signs in with one shared account, there are no separate users to delete — the only way to revoke access is to change the shared password or contact support.
When a colleague leaves or shouldn't have access any more, admins can delete them from Settings → Manage Users. To make sure nothing is orphaned, 4admin requires you to hand off their policies and LoAs to another user as part of the delete flow.
The flow
- In Manage Users, click the trash icon next to the user you want to delete
- The delete modal opens with a warning trash icon to make sure you know this is destructive
- Read the headline: "This user will be deleted as soon as their records are reassigned. This cannot be undone."
- Pick the destination owner from the Re-assign all data to dropdown. Every policy and every LoA owned by the user being deleted will be moved to this person
- Click Re-assign and delete user
The modal closes and you'll see a toast confirming the handover is running in the background.
What happens next
The reassignment runs as a background job on the server, so you can keep working:
- Every policy owned by the user moves to the destination owner
- Every LoA owned by the user moves to the destination owner (kanban cards and chips will reflect the new owner once the move completes)
- Once everything is moved, the user is removed from your team list and their login is revoked
- A notification lands in your notification bell summarising the result, e.g. "Reassigned 37 policies and 12 LoAs, user deleted"
If anything fails during reassignment, the notification reflects that and the records that were already moved stay moved (so retrying is safe).
Why there's no "delete only" option
Deleting a user without reassigning would leave their policies and LoAs sitting under a deleted user ID, invisible in the UI but still in the database. To avoid that mess, 4admin only offers the reassign-then-delete flow.