In Textura today, deactivating a user typically blocks sign-in and system use but may leave their project permissions intact in the system. If the account is later reactivated, those permissions are restored. While this can simplify re-onboarding (e.g., after leave or a department move).
We’re exploring enhancements to the user deactivation workflow to make it easier to:
- Immediately clean up all open tasks assigned to the deactivated user
- Ensure no residual permissions remain (reducing audit noise and reactivation risk)
- Prevent future project-level tasks from being created for deactivated users
- Allocate time to remove project-level permissions for deactivated users, especially those spanning multiple projects.
Question to the community:
- What information would be most helpful to display during the deactivation flow (e.g., projects, roles, ownerships, pending approvals, in-progress tasks)?
- What parts of the current deactivation process work well, and where do you see opportunities to improve?