When a team member leaves the company, disable them — don't delete. Disabling removes access while preserving all their history.
Open the team page
Go to Settings → Team and pick the member.
Disable the account
Click Disable (or toggle their Active status to off) and confirm.
Disabling is reversible — re-enabling the same email at any time restores access.
What disabling does
| Effect | Detail |
|---|---|
| Can't sign in | Their session is invalidated immediately |
| Removed from future job assignments | Open jobs assigned to them are unassigned automatically so they don't go undone |
| Stops appearing | In the dispatch board, the active team list, and assignment dropdowns |
What disabling preserves
| Preserved | Detail |
|---|---|
| Past job history | Every job they ran, every photo, every signature — nothing is deleted |
| Time clock records | Past timesheets stay intact for payroll and audit |
| Team membership record | Still in the database, just inactive |
| Customer communications | Every SMS, email, and call recording they sent |
Why not delete
Deleting a user would break referential integrity — their name on past jobs, time entries, and communications would orphan. Disabling is the right move.
If you absolutely must remove a user record (e.g. legal request), contact support for the GDPR/privacy-compliant flow.
Reactivating
If a former tech rejoins:
- Settings → Team → view Archived or Inactive.
- Find them.
- Re-enable.
Their old role and basic profile come back. They'll need to sign in fresh (likely set a new password since their old one's been forgotten).
Common patterns
| Scenario | What to do |
|---|---|
| Voluntary resignation | Disable immediately on their last day so they can't access systems after they leave |
| Termination for cause | Disable BEFORE the conversation — lock out access first |
| Seasonal layoff | Disable during the off-season, re-enable when they come back |
| Lost device | Don't disable the user; just revoke their session. Talk to support for the right action. |