Appearance
Telegram
People bring their own Telegram bots, made with @BotFather: one for their notifications (Account → Telegram), and one per agent its editors want on Telegram (see the guide). The server needs no setup of its own; the bots' tokens are stored encrypted with the master key.
How Telegram reaches the server
- With a public HTTPS address (
CREWHALL_PUBLIC_URL, on port 443, 80, 88 or 8443), Telegram calls/api/hooks/telegram/<bot>when someone writes to a bot, with a secret CrewHall gave it. - Otherwise (a laptop, a private network), CrewHall asks Telegram for new messages, one long poll per bot. Nothing has to be opened to the internet. Run one API server in that case: two would take turns answering.
After changing CREWHALL_PUBLIC_URL, a bot switches when its token is saved again.
Notifications go out on the same schedule as emails (CREWHALL_NOTIFICATION_MAIL_SECS, default every 20 seconds); 0 turns both off. Nothing is sent about notifications from before a bot was added.
Privacy
Chats with a bot aren't end-to-end encrypted: what people choose to get on Telegram, and what they write to agents there, passes through Telegram. The privacy policy says so. Using it is each person's choice, and each agent editor's.
