Withdraw access and delete data

Review the scope before confirming a removal. A Chat seat withdrawal, a membership removal, an account deletion and an organization deletion affect different data.

Check ownership and retained records

Transfer organization and Chat ownership before removing an owner. Historical orders and records subject to financial or security retention remain governed by their retention rules.

Choose the intended scope

Goal	Effect
Withdraw a Chat seat	Removes Chat access; keeps membership and user data.
Withdraw portal access from an Entra-assigned person	Removes portal membership; directory-managed service access and data remain.
Remove an invited organization member / leave the organization	Revokes membership and requests removal of their private Chat data in this tenant; other organizations and AUTARQ ID remain separate. Shared artifacts transfer to the seated Chat owner.
Delete the account	Discovers the person’s affected Chat tenants, verifies cleanup and removes the AUTARQ ID account last. Ownership must be resolved first.
Delete the organization	Suspends access, applies the displayed cancellation period and verifies tenant cleanup before infrastructure and identity finalization.

Start the request

Use the action for the intended scope: Chat or People for access, Organization for leaving or organization deletion, and the offered account-deletion control for the account. Available controls depend on your role, ownership, environment and deletion-service readiness.

For directory-managed people, removal begins in Entra. An admin block retains records; directory deletion can request verified erasure for an AUTARQ-provisioned identity. Check the directory lifecycle first.

Follow the cancellation period

Organization deletion normally allows seven days to cancel. Follow the exact deadline on Deletion status. An authorized AUTARQ system administrator can explicitly end this period early. Once irreversible processing starts, cancellation is no longer available.

Verify completion

Follow the request reference and subsystem progress. An accepted request is still in progress until all required systems confirm cleanup. Provisioning or identity operations can keep deletion waiting. Resolve the reported cause with support; repeated requests do not bypass checks.

If cancellation was accepted, wait for restoration to finish before treating access as recovered. For a blocked request, send support the request reference and displayed error, without private data or credentials.