Offboard a User
Cleanly remove a departing person's access while preserving their work and history.
#Purpose
Protect the business when someone leaves.
#When to use this
When an employee or collaborator departs.
#At a glance
| Detail | Value |
|---|---|
| Required permissions | User management (CEO or admin) |
| Administrator level | CEO / Admin |
| Portal areas used | Users, User lifecycle |
#Workflow
1
Reassign work
Leads/tasks/tickets.
2
Deactivate
Block access.
3
Force sign-out
End sessions.
4
Delete if final
Soft delete.
#Step by step
1
Reassign their work
Move active leads, tasks, and tickets to other owners.
2
Deactivate the account
Suspend their access immediately.
3
End their sessions
Ensure they are signed out everywhere.
4
Delete if appropriate
Soft-delete the user; history is preserved.
#Approval points
No formal approval gate
This administrative action does not require a separate sign-off, but review carefully before applying changes.
#Security notes
Security considerations
- Deactivate the moment access should end.
- Reassign ownership so nothing is orphaned.
- Review what the person could access and confirm it is revoked.
#Best practices
- Have an offboarding checklist.
- Reassign before deactivating.
#Common mistakes
- Deleting before reassigning work.
- Leaving sessions active.
#Troubleshooting
| If this happens | Try this |
|---|---|
| Their work is now unassigned | Reassign it to an active owner. |
#FAQ
Should I deactivate or delete a departing user?
Deactivate immediately; delete (soft) once you are sure, so history is preserved.
#Keep exploring
#Related admin guides
#Business modules & workflows
Getting Started
Initial setup.
Platform Overview
How the OS fits together.
Knowledge Base
Task-level how-tos.
Business Workflows
End-to-end processes.
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?