Team and organization
Member access controls
Owner controls can pause a member, separately deactivate their Stand-in coverage, restore access, transfer ownership, or permanently remove the member while preserving team records.
- Availability
- All plans
- Configured in
- Dashboard → Team → actions beside a non-owner member
- Category
- Team and organization
- Reference status
- Current
Before you begin
Plan availability: All plans.
Prerequisite: Organization-owner access; actions are not offered on the owner’s own row.
Key boundary: Remove member is destructive for that account’s organization access. Use Disable when the intended change is temporary.
Available owner actions
| Action | Effect |
|---|---|
| Disable | Revokes organization dashboard and real-time chat access; the dashboard signs the member out when it receives an access denial. Their record remains so access can be restored. |
| Enable | Restores an existing disabled member’s organization access. |
| Deactivate Stand-in coverage / Activate Stand-in coverage | Stops or permits coverage by that member’s enabled Stand-ins without changing the human member’s login state. |
| Make owner | Transfers the single owner role to that member; the current owner becomes a regular member. |
| Remove member | Revokes membership immediately and queues the sign-in account for deletion with retry; past team records remain. |
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 access changes
- Ownership transfer and removal open an explicit confirmation dialog naming the affected person.
- A disabled or removed member’s next protected dashboard API request is denied even if the browser still holds an unexpired access token, and the dashboard signs the member out.
- Protected requests use the current organization membership rather than an older organization value from a token or cached profile.
- New rep chat and notification connections require active membership. Existing connections recheck it before traffic and periodically while idle; revoked or unverifiable access closes the connection.
- 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.
- Access revocation does not promise an instantaneous network disconnect: previously authorized work may finish.
- These access checks do not revoke identity-provider login or refresh tokens, or transfer a member’s existing chat assignments.
- Removing a member is not the same as deleting the whole organization.