This article explains how Rocketlane handles deactivated users. It outlines where they're completely removed from the system and where they're labeled with a "deactivated suffix" to maintain historical context. For example: You can't add a deactivated user to a project or template, but tasks assigned to them before deactivation display with a "deactivated icon" for reference.
Here is what it looks like 
Module | Shown in the UI | Removed from the system |
| Projects | Deactivated users are not removed from a project, including cases where the user is the project owner. The UI displays the user's name with a (deactivated) suffix." | Project invitations will not show other deactivated users, even in search. If a deactivated user is removed from a project, they cannot be added again." |
Tasks | Deactivated users are not removed from task assignees. The UI displays the user's name with a (deactivated) suffix. | Tasks cannot be assigned to a user after they are deactivated. Assignee dropdowns will still show deactivated users if previously assigned, but will not display other deactivated users, even in search. |
Single and multi user fields | Deactivated users are not removed from these fields if their value is already present. The UI displays the user's name with a (deactivated) suffix. | Once a deactivated user is removed from a user field, they cannot be added again. User fields will still display deactivated users if previously selected but will not show other deactivated users, even in search. |
Filters |
| NA |
Resource management |
| NA |
Templates | NA | When a team member is deactivated, we need to remove them as assignees from any tasks and eliminate them from the resource allocation page, deleting any allocations the user had from the template. |
Reports | Any team member based report should display deactivated users as a row only if there is data to show for that user; deactivated users without any data will not be included in the report. |