> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tessact.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# User Lifecycle Management
> Invite, activate, deactivate, and review users safely from the Tessact admin directory.
## Overview
The **Users** directory is the main admin surface for the user lifecycle. It combines search, filters, bulk actions, row-level actions, and a user details sheet so admins can manage access without jumping between multiple settings pages.
***
## Guide: Invite A User
Use **Invite user** from the action bar to add someone to the organization.
The invite flow captures:
* **email**
* **first name**
* **last name**
* **display name**
* **organization role**
After that, Tessact can also assign the person to one or more workspaces during the same flow. Workspace assignment is optional, which is useful when onboarding and access approval happen in separate steps.
If you are not ready to decide workspace access yet, invite the user first and handle workspace membership later from the directory.
Go to **Admin → Users** and use **Invite user** from the top action bar. This keeps onboarding anchored in the same directory where you will later review activity, role, and workspace access.
Add the person's email, first name, last name, display name, and initial organization role.
Use the second step only if the person should land in one or more workspaces immediately. Choose the target workspaces and the shared workspace role for this invite.
Submit the invite when the role and workspace choices are correct. If access approval is still pending, skip workspace assignment and add memberships later from the directory.
***
## Review Existing Users
The directory is organized around four high-signal columns:
| Column | What it shows |
| --------------- | --------------------------------------- |
| **Name** | Identity and email |
| **Role** | Current organization role |
| **Workspaces** | Where the user already has access |
| **Last active** | Whether the account is still being used |
These columns are enough for most admin decisions: who the person is, how much power they have, where they can work, and whether the account is still active in practice.
***
## Use Filters For Real Reviews
The **Filter users** control opens the user filter bar. Current filters include:
* **Status**: all, active, deactivated, no workspace
* **Activity**: any activity, active in 7 days, active in 30 days, inactive 30+ days, never logged in
* **Workspace**
* **Organization role**
These filters are the fastest way to run a review like:
* users who never logged in
* users with no workspace access
* inactive users in a specific workspace
* everyone holding a specific organization role
***
## Activate Or Deactivate Users
Tessact supports status changes from both row actions and bulk actions.
* Use **Deactivate user** when a person should temporarily or permanently lose access.
* Use **Activate user** when returning access to an existing account.
This is preferable to deleting and recreating accounts because it preserves the identity record and keeps future audits clearer.
Deactivation changes whether a person can use the product, but it does not automatically redesign your workspace access model. Review memberships and role assignments too.
***
## Inspect A User In Detail
Selecting a row opens a details sheet. Use it when the table summary is not enough and you need to verify a specific person's profile or access context before changing anything.
This is especially useful when:
* a user appears in several workspaces
* role assignment is unclear
* support requests are tied to the wrong display name or identity data
***
## Common Lifecycle Reviews
Use the directory for three recurring admin reviews:
### Onboarding
1. Invite the user with the correct organization role.
2. Decide whether workspace access should be added immediately or later.
3. Confirm the user appears with the expected role and membership state.
### Dormant account cleanup
1. Filter by **inactive 30+ days** or **never logged in**.
2. Check whether those users still need workspace access.
3. Remove workspace access or deactivate the account, depending on the case.
### Role verification
1. Filter by organization role.
2. Open edge cases in the details sheet.
3. Use **Assign role** only when admin responsibility actually changed.
***
## Best Practices
* Invite first, then add workspace access only where it is justified.
* Use **activity filters** before deactivating dormant accounts.
* Prefer deactivation over duplicate-user creation.
* Keep organization roles limited to the people who truly need them.
* Review users with **no workspace** regularly so org seats are not wasted on unused accounts.
***
## Next Steps
Manage workspace access cleanly from the users directory.
Speed up org-wide user maintenance with selection-based actions.