Member access controls

Available owner actions

What happens to shared records

• Past team conversation transcripts remain in History after disabling or removal.
• The responder attribution on older conversations is preserved.
• Knowledge-base ownership is transferred or otherwise resolved so shared resources are not orphaned.
• Deactivating Stand-in coverage changes eligibility for new AI conversations; it does not erase historical conversations.

Choose disable or remove

Disable is reversible and appropriate for leave, investigation, or temporary access suspension. Remove is the permanent offboarding path. Stand-in coverage is independent: an active person can remain able to answer human chats while their Stand-in coverage is inactive.

Confirmation and immediate effect

• Ownership transfer and removal open an explicit confirmation dialog naming the affected person.
• Disabled members are signed out and receive guidance to contact the owner.
• New authorization checks use the changed status immediately rather than waiting for a later billing period.
• The owner cannot run these row actions against themselves; self-deletion follows the account deletion rules.

Boundaries

• Access controls do not delete retained customer conversations.
• Stand-in enablement does not override site routing or plan quota.
• A disabled member cannot re-enable themselves.
• Removing a member is not the same as deleting the whole organization.

Related features

• Team members and roles — The Team page shows who belongs to an organization, what access each person has, and the current state of their human and AI coverage.
• Member invitations — Owners invite new organization members by email and can optionally require the invitee to use an enabled identity provider such as Google.
• Account and organization deletion — The profile danger zone deletes a regular member account, or—when the owner is alone—permanently deletes the entire organization and its customer data.