Manage Profile, Password, Language & Notifications
Update your Wemblo profile, password, interface language, currency display, notification settings, and active sessions.
STEPS
- Open the profile or account menu.
- Review name, business email, phone, language, and notification preferences.
- Change the password using a strong unique value.
- Review active sessions where available.
- Save and sign in again if requested.
- Use a separate account for every person.
Never share passwords or verification codes.
Who should use it
Workspace owners, billing users and authorized account users.
Where to find it in Wemblo
Wemblo -> Profile / Account Settings
Before you begin
- Confirm the correct workspace and account owner.
- Review the current plan, term and usage.
- Use verified billing or privacy contact details.
- Do not send passwords, permanent tokens or payment-card details.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Account | One person's sign-in. |
| Workspace | Business environment. |
| Credential | Password, key, token or secret. |
| Role | Controls access. |
| Audit | Review of users, integrations and activity. |
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 |
|---|---|
| Change is not active | Workspace, effective date, payment verification or manual review. |
| Usage looks incorrect | Base allowance, add-on allowance, provider usage and reset date. |
| Request cannot be completed | Account authority, required verification and outstanding billing/security review. |
| Notification is missing | Billing contact, email, app notification and spam folder. |
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: