Configure Roles & Module Permissions
Configure least-privilege View, Create, Edit, Delete, and Manage access across Wemblo modules.
Overview
Recommended user types include Workspace Owner, Workspace Manager, Agent, Marketing User, Billing User, and Developer. Protect billing, provider connections, AI configuration, recordings, transcripts, API keys, webhook secrets, and user management.
Who should use it
Workspace owners, managers, agents and authorized mobile or reporting users.
Where to find it in Wemblo
Wemblo -> Teams -> Permissions
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 | User group. |
| Agent | Authorized user. |
| Mobile App | Android or iOS workspace access. |
| Report | Operational summary. |
| Usage | Plan capacity and monthly activity. |
Step-by-step instructions
- Open Wemblo -> Teams -> Permissions.
- Confirm the active workspace and your role.
- Create or select the user, team, task, device or report.
- Configure only the required access or filters.
- Save.
- Test with a non-owner account or fictional record.
- Review notifications, assignments or report values.
- Document the responsible owner.
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: