Offboard a Team Member Safely
Reassign work, disable the user, revoke sessions and provider access, rotate credentials, and preserve required records.
STEPS
- Identify the leaving user and effective time.
- Reassign open conversations, tasks, leads, campaigns, and workflows.
- Transfer team or workspace ownership where required.
- Disable the account and revoke sessions.
- Remove provider, mobile, API, and webhook access.
- Rotate any credential the user knew.
- Preserve necessary audit and business records.
Who should use it
Workspace owners, managers, agents and authorized mobile or reporting users.
Where to find it in Wemblo
Wemblo -> Teams
Before you begin
- Use a unique user account.
- Confirm the active workspace and role.
- Use test users or fictional customer data.
- Protect mobile devices and sensitive reports.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Team | Reusable permission and assignment group. |
| Member | User assigned to the team. |
| Permission | Allowed module or action. |
| Queue | Work routed to the team. |
| Owner | Manager responsible for the team. |
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Common issues and solutions
| Issue | What to Check |
|---|---|
| User cannot see the module | Team, role, active workspace and account status. |
| Assignment or notification is missing | Owner, device/browser permission and routing rule. |
| Report is empty or different | Date range, PKT, workspace, provider definition and sync delay. |
| Former user still has access | Disable account, revoke sessions and rotate shared credentials. |
Security, privacy, consent, cost and provider notes
- Use only data the business is authorized to process.
- External provider charges, policies, approvals, limits and availability remain separate.
- Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
- Use human review for sensitive, regulated, urgent, financial or final decisions.
Last reviewed: