Chat: channels and direct messages for your organisation

Every organisation gets Chat: a Slack-like app at its own address, built from the same app spec as everything else, with membership security generated by the platform.

What it does

• Channels: public, private, or a group of named people; topics, archiving, and an admin role per channel.
• Direct messages: one conversation per pair of people, created on first message.
• Threads and reactions: reply under a message; react with an emoji.
• Attachments: files live in the organisation's storage under the channel; only channel members can open them.
• Unread and mentions: unread counts per channel, a bell with your mentions, replies and direct messages, and desktop notifications when you allow them.
• Presence: who is online and who is typing, live.

Email when you are away

Every ten minutes a digest job mails you the mentions, replies and direct messages that have stayed unread for ten minutes, one email per person, with a link to each channel. The per-channel setting Email me lets you turn this off for a channel; a muted channel never notifies. The digest is a standard kind: "digest" job of the app spec, so any app you build can have the same.

Who can see what

Membership follows the organisation: everyone who joins the org can open Chat and sees public channels; private channels and direct messages are visible only to their members, enforced by row-level security in the database rather than by the interface. Chat runs at chat-<organisation>.nibor.io and appears in the Workspace and in Nibor OS.