Team and operator seats
The main account creates operator seats for the team and decides which shops each one can reach. Operators cannot register themselves.
Creating a seat
Sidebar · Team›New operator
- Enter the operator name (letters and digits, e.g.
kefu), an initial password, and optionally a display name; - On save the system builds the full login:
name@mainAccountUserId— for examplekefu@1000; - Hand that login and the initial password to the team member and ask them to change it on first sign-in.
Only the main account sees and uses the Team page.
Assigning shops
A new seat has no shop permissions at all — you must assign before they can start replying. In the list, click Assign shops on that seat and tick the allowed shops (saving replaces the previous selection).
- An operator only sees and acts on conversations, products, orders and to-dos of assigned shops;
- The main account always sees every shop under the account;
- Any unauthorized access is blocked server-side.
Disabling and deleting
- Disable — keeps the seat and its settings but revokes the session immediately: the person is signed out on the spot;
- Enable — restores access;
- Delete — removes the seat permanently, also revoking the session immediately.
When someone leaves, disable first and delete only after the handover is complete.
Main account vs operator
| Capability | Main account | Operator |
|---|---|---|
| Handle conversations | All shops | Assigned shops only |
| Authorize / delete shops | Yes | No |
| Team | Yes | Entry not visible |
| Credits and billing | Yes | Entry not visible |
| To-do rules | Add and edit | Read-only |
| Team quick replies | Add and edit | Read-only (can use) |
| Personal quick replies | Own set | Own set |
| Change own name and password | Yes | Yes |
| Change phone / email | Yes | Managed by the main account (read-only) |