Set up team mode
Let several people work in one ChatPilot, each with their own sign-in and role.
Team mode turns one ChatPilot into a shared inbox for a team. It runs on a server everybody can reach (see the Docker setup in Install ChatPilot), and each person signs in with their own e-mail address. It is part of the Business plan; without a licence (developer mode) it works without a seat limit.
Team mode is off by default. An install for one person keeps working with its link, exactly as before.
Switch it on
- In
config.yaml, setteam: {enabled: true, code_mailbox: <one of your mailboxes>}. The sign-in codes are sent from that mailbox, so it must be one you added under Settings → Mailboxes. Restart ChatPilot. - Open Settings → Team. It says not on yet.
- Type your name and e-mail address and press Add me as owner.
From that moment the old link stops working and everybody signs in, you included.
Signing in
On Sign in to ChatPilot, type your work e-mail address and press Send me a code. A 6-digit code arrives by mail; it works for 10 minutes. If you set up an authenticator app, it then asks for the code from that app too.
A device stays signed in for 30 days (team.session_days). Sign out on the Team card, or on You in the team, signs that device out.
Set up an authenticator app (on the Team card for owners, on You in the team for everybody else) adds that second step: scan the code with Google Authenticator, Microsoft Authenticator, 1Password or a similar app, type the code it shows and press Switch on. A member who lost their phone: an owner presses Reset next to them, and they set the app up again at their next sign-in.
Add the others
On Settings → Team, type a name and e-mail address, pick a role and press Add member. They sign in with that address; there is no password to send them.
| Role | What they see and do |
|---|---|
| Owner | everything: every work chat, settings, connected systems, rules, the licence |
| Lead | every work chat of the team, and gives chats to members |
| Member | the chats of their own accounts and the ones given to or shared with them |
You can change a role at any time in the list. The card shows how many seats your licence has (for example 3 of 5 seats); a disabled member doesn't use one.
Leads and members read, draft, reply, schedule, mark done, snooze, and use Today, Tasks and People, all over the chats they see. Settings, connected systems, rules, templates, discussions and switching a chat's AI or auto-answer stay with owners.
Whose account is it?
Under Accounts on the Team card, say for each connected account (a mailbox, a Slack workspace, Telegram, WhatsApp) which member it belongs to. A chat belongs to the member whose account it came in through, until someone gives it to someone else (Share the work).
Each member can bring their own Telegram and WhatsApp:
- Settings → Telegram → ＋ Add account: a short name (their first name, say), their phone number and the code Telegram sends them.
- Settings → WhatsApp → ＋ Add account (once the first device is linked): a short name, then the member scans the QR code on their phone under Linked devices. On a server, WhatsApp sees a data-centre address, which is riskier for the number.
Each account's chats stay apart from everybody else's, also when two members are in the same group, and they start switched off like every new chat. Remove disconnects the account; the chats already stored stay.
You in the team
Leads and members have their own page, You in the team: who they are signed in as, what they see, their own accounts with the 🔒 Private switch, the authenticator and Sign out.
Checked against ChatPilot 0.1.0b1. Report a problem with this page