Deleting a user on the Assignar dashboard removes their record permanently. In most cases you should deactivate a user instead, which removes their login but keeps their record so you can bring them back. Delete only when you need the record gone, for example a duplicate created by mistake. This article explains how. You need the Add Users access.
Before you delete a user on the Assignar dashboard
Deactivate first. Only deactivated users can be deleted. See How do I archive or reactivate a user on the dashboard?.
Deleting can't be undone. The user and all their links to other records are removed.
Users with history usually can't be deleted. If the user is linked to records such as timesheets, orders or dockets, Assignar won't delete them. Leave them deactivated.
Delete a user on the Assignar dashboard
To delete a user on the Assignar dashboard:
Go to Resources > Users and open the Workers or Dashboard tab.
Change the Active filter to Deactivated.
Find the person and click the menu (⋮) on their row.
Click Delete.
The Delete User window asks "Are you sure you want to permanently delete <name>? This will also remove all their relations to other entities." Check the name.
Click Delete.
The dashboard shows "User deleted successfully".
Why can't I delete a user on the Assignar dashboard?
Deleting a user on the Assignar dashboard fails in these cases:
There's no Delete option. The user is still active. Deactivate them first, then switch the filter to Deactivated.
"Only deactivated users can be permanently deleted." The user is still active.
"Cannot delete this user because they are referenced by other records." The user is linked to other records, such as timesheets, orders or dockets. Keep them deactivated instead.
"Failed to delete user": reload the page and try again.
Delete a duplicate worker on the Assignar dashboard
If the same worker was added twice on the Assignar dashboard, keep the record that has their timesheets and allocations. Fix that record's email if needed, then deactivate the other one and delete it if it has no history. Don't delete and re-add a worker to fix a login problem; see How do I help a worker who can't log in to the mobile app?.

