User Cleanup
Regularly review users and access, removing or deactivating accounts that are no longer needed.
#Purpose
Keep access tight and current.
#When to use this
As part of routine maintenance and after departures.
#At a glance
| Detail | Value |
|---|---|
| Required permissions | User management (CEO or admin) |
| Administrator level | CEO / Admin |
| Portal areas used | Users, Roles |
#Step by step
1
List users and roles
Review who has access and at what level.
2
Identify stale access
Find accounts no longer needed or over-privileged.
3
Deactivate or adjust
Suspend unused accounts and right-size roles.
4
Reassign and delete
Reassign work, then soft-delete departed users.
#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
- Stale accounts are a security risk — deactivate them.
- Apply least-privilege when adjusting roles.
#Best practices
- Review users on a cadence.
- Deactivate promptly when access is no longer needed.
#Common mistakes
- Leaving departed users active.
- Too many admins.
#Troubleshooting
| If this happens | Try this |
|---|---|
| A user still has access after departure | Deactivate the account and end their sessions. |
#FAQ
Deactivate or delete stale accounts?
Deactivate first; soft-delete once you are sure, preserving history.
#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?