User lifecycle and audit

Use the row's three-dot menu for an individual account or Bulk Actions for a reviewed selection. Lifecycle actions are available only when your role is permitted to manage the target user.

Deactivate or delete

Temporarily deactivate sets the account inactive, records a deactivation date, and replaces its password so the previous password no longer works. The account and audit history remain available, and an authorized administrator can reactivate it later.

Permanently delete removes the user through the deletion workflow. Treat it as irreversible: it can affect assignments, ownership references, reporting, and audit interpretation. Deactivate first when access must stop but retention requirements are uncertain.

Both buttons require confirmation, but the lifecycle dialog contains both choices. Verify the action label, selected-user count, identities, and retention approval before confirming.

Danger

Permanent deletion is not a substitute for deactivation. Confirm legal, audit, integration, and record-retention requirements before deleting any user, especially through a filtered bulk selection.

Reactivate a user

Filter status to Inactive, open the row menu, and select Reactivate User. After confirmation, TEKControl marks the account active and opens a password-change dialog. Set a new policy-compliant password and communicate it through an approved secure method.

Reactivation does not redesign the user's access. Review roles, clients, sites, posts, and modules before allowing the person to sign in again.

Review login audit

Select Login Audit to view recent login entries recorded for the user. Each entry displays the login date and time in UTC and the recorded IP address when available. No entries can mean the user has never logged in or no retained audit rows are available.

Compare UTC timestamps carefully with local incident times. A login record shows authentication activity; it does not by itself prove every action performed in the session.

Review change history

Select Change History to inspect recorded changes to the user entity and its audited assignments. Use it to identify who changed profile data, roles, clients, sites, posts, modules, status, or other recorded values.

Audit coverage can differ by operation and historical version. Correlate login audit, change history, site activity, and identity-provider logs when investigating access.