Three roles, clear authority
OWNER and ADMIN read and write; MEMBER is read-only and gets 403 in user management.
- Role
- Team
—PRODUCT
Manage the team behind the shared inbox by role, so it is clear who sees what and who gets notified.
OWNER/ADMIN/MEMBER roles, seats, per-person Telegram/SMS notification addresses and the customer-facing brand in one place.
—SUMMARY
Manages the team behind the shared inbox with roles, seats and notification addresses.
01HOW IT WORKS
Each step is one screen in the panel; nothing goes live without confirmation.
A user is created directly as ACTIVE with a temporary password; no email invitation is sent. Role and status can be edited later.
Enter a Telegram chat ID and phone per person; leaving them empty turns that channel off. A user can change only their own address.
Organisation name, logo and email sending identity define customer-facing surfaces; the logo does not accept SVG.
02WHAT IT DOES
The three capabilities below are today’s scope; the sample dialogue is fictional and contains no real customer data.
OWNER and ADMIN read and write; MEMBER is read-only and gets 403 in user management.
Seats depend on the plan; only ACTIVE users count. When full, the panel returns 409 and says “extra seat or higher plan”.
A Telegram chat ID and phone are set per user; the list does not return them, only whether they exist.
03THE DIFFERENCE IS IN THE DETAILS
23 items, each tied to a rule, setting or automatic behaviour in today’s product. No unsupported number, ratio or promise appears in this list.
There are three roles: OWNER, ADMIN and MEMBER; a new user defaults to MEMBER.
OWNER and ADMIN read and write; MEMBER is read-only and gets 403 when adding, updating or deleting users.
The last active OWNER cannot be demoted, deactivated or deleted; a user cannot change their own role/status or delete their own session.
An agency can manage a client organisation’s team (name/role/status) but cannot reset its password.
Seats are plan.teamUserLimit plus active extra seats; only ACTIVE users count, and when full the API returns 409 with “extra seat or higher plan”.
There is no invitation flow; a user is created directly as ACTIVE with a temporary password, and no email invitation is sent.
A password is 10–128 characters, stored with PBKDF2-SHA256 at 210,000 iterations; the audit trail records only a “password changed” note.
The “must change on first login” text exists in the UI; no server setting or flow enforcing it was found.
A password reset can generate 16 characters; it is shown once and never written to logs or localStorage.
Removal is a soft delete: status=DISABLED plus archivedAt; PII in the audit trail is anonymised.
A Telegram chat ID (5–32 digits) and phone are set per person; leaving them empty turns the channel off, and a user changes only their own address.
The user list does not return phone/Telegram, only whether they exist.
Only active OWNER/ADMIN receive handover notifications; MEMBER does not.
There is no 2FA/TOTP; sign-in is password plus Turnstile.
The seat check exists only in POST /users; no seat check was seen when PATCH changes DISABLED to ACTIVE.
The profile is not a personal user profile; it manages the organisation’s customer-facing brand. Name, email and avatar are not edited here.
The email sending card is at the top, followed by password change, logo, name/plan and contact summary.
Changing the password requires the current password, a new password of at least 10 characters and a repeat; a wrong entry says “Your current password is incorrect”.
Changing the password does not invalidate existing tokens; token lifetime is 12 hours.
The logo is PNG/JPEG/WebP and at most 2 MB; SVG is rejected because it can embed code, and the old logo is kept if upload fails.
The logo is visible to customers: widget header/avatar, customer emails, voice greeting and comment replies; the panel brand comes from the agency.
Email can use the platform default, Resend or SMTP; there is a sender name/address and a test email, and internal-network SMTP addresses are rejected for security.
There is no 2FA, session/device management or “close all sessions”.
04CONTROL AND SECURITY
These are this surface’s current security behaviours; no general “GDPR compliant” certificate is claimed.
The last active OWNER cannot be demoted, deactivated or deleted, so the organisation cannot be left unmanaged.
MEMBER gets 403 when adding, updating or deleting users and cannot change the team by mistake.
A 16-character temporary password is shown once and is never written to logs or localStorage.
There is no 2FA/TOTP, device management or “close all sessions”; changing the password does not invalidate existing tokens, which live for 12 hours.
05WHICH PLAN
Seats depend on the plan: Starter 3, Growth 5, Business 20. The extra-seat fee is on the plan cards; the trial may not enforce a seat cap (inventory observation).
All amounts are monthly and exclude VAT. See the plans page for the current list and calculator. Plans and calculator →
06FAQ
+RELATED POSTS
Posts from the same topic cluster that complete this page. Team & roles posts.
A plain guide to what an AI customer agent does, how it answers from a knowledge base and when it hands a conversation to a person.
Both appear in a message box, but they do different work. A guide to the difference between a rule-tree chatbot and an assistant that answers from a knowledge base.
A practical comparison for SMEs: when a call center makes sense, when an AI voice assistant does, and how volume, scope, handover, cost and data should decide.
Try free for 14 days without a credit card; we will do the first setup together.