Skip to main content

​
Overview

Removing a user from a workspace is more precise than deactivating the org account. Use it when the person should stay in Tessact, but should no longer work in this specific workspace.
Remove users from workspace confirmation

Workspace removal confirmation flow

​
When Removal Is The Right Action

Remove a member when:
  • they changed teams
  • project work in this workspace ended
  • a temporary collaborator no longer needs access
  • the workspace member list has become broader than the current operating team
Do not use removal when the real issue is an org-wide access problem.

​
Guide: Remove Members Without Causing Drift

1

Select the member or cohort

Start from Members, then select the people whose workspace access should end.
2

Use the workspace-level removal action

Open Remove users from the selected-member action bar and confirm the exact removal scope.
Workspace removal modal

Workspace member removal confirmation

3

Check for follow-up changes

After removal, verify whether the person still needs org access, whether ownership should move to someone else, and whether any elevated roles should be reviewed elsewhere.

​
Safety Checklist

Before removing someone, verify:
  1. they are not the only person handling an active workflow in this workspace
  2. the workspace still has enough responsible members after the change
  3. the change should be local to this workspace, not org-wide

​
Best Practices

  • Remove workspace access as soon as the workspace purpose no longer fits.
  • Review role and ownership implications before large cleanup passes.
  • Prefer workspace removal over broader account actions when the issue is local.

​
Next Steps

Workspace membership reviews

Return to the full member-review flow.

Workspace governance

Put member removals in the context of broader workspace hygiene.