Leaving or removing a user
Removing a user takes them off the agency and frees their seat. Submissions they owned have their assignment cleared (you'll see them as unassigned). For temporary suspension, disable sign-in instead of removing.
In short: Open your users settings, find the user, remove. Their seat frees up, their submissions become unassigned.
When to remove vs disable
| Situation | What to do |
|---|---|
| Employee left the agency | Remove from your account |
| Employee on extended leave | Disable sign-in (keep access) |
| Account compromised | Disable sign-in immediately, then investigate |
| Role changed (need different permissions) | Edit role, don’t remove |
| Want to free a seat | Remove |
Removing takes the user off your agency. Disabling sign-in keeps them on the agency but blocks login — useful for temporary scenarios where you want them back later.
Remove a user
-
1
Open your agency’s users settings.
-
2
Find the user.
-
3
Click the remove action.
-
4
Confirm the prompt.
-
5
They’re off the agency. Their seat frees up.
If your agency was their only SALT account, their sign-in is fully removed — they can’t sign in to SALT at all.
What happens to their Submissions
When a user is removed, Submissions where they were the assignee become unassigned:
- The Submission stays in your agency’s list as normal
- The assignee field becomes empty
- The Submission appears in the Unassigned Saved View
- Default notification routing for that Submission goes to no one until you reassign
You should triage unassigned Submissions promptly. See Assigning a Submission for the reassignment flow.
Bulk reassignment before removal
If you know in advance that you’re removing someone, reassign their Submissions first to avoid the unassigned cliff:
-
1
From the Submissions list, filter by assignee = the departing user.
-
2
Bulk-reassign to a different teammate.
-
3
Once reassigned, remove the user.
Disabling sign-in (alternative to removal)
For temporary lockouts (PTO, leave of absence, security investigation):
-
1
Open the user’s record.
-
2
Toggle off their sign-in access.
-
3
They’re locked out — can’t sign in — but they remain on the agency.
-
4
Re-enable sign-in when they should return.
This preserves their assignments, role, and history. The seat stays consumed.
Self-removal (leaving an agency)
A user can sometimes leave an agency themselves from their account settings. This option may not be exposed in every configuration — for situations where it isn’t, ask an admin to remove you.
Common questions
Will the removed user’s name still appear on past Submissions? Submissions retain their history — you may see “Created by Jane Smith” on Submissions from before her removal. The reference to her doesn’t break.
Does removing them delete their Notes and Comments? No. Notes and Comments they authored remain on their Submissions, attributed to them historically.
Can the removed user reactivate themselves? Once removed, they need a fresh invitation to come back. Their old Access doesn’t restore — re-invite if needed.
What if I accidentally remove the wrong user? Re-invite them. They’ll need to set up access again, but their seat opens immediately when re-invited. Past Submissions they were assigned to remain unassigned until manually reassigned.