Kemble Work — collaboration for companies
Channels, threads, files, search, voice and automation, with a permission model and an audit trail that survive contact with an enterprise security review.
Conversation
The parts people touch every hour.
- Channels and categories
- Public, private, announcement and voice channels, grouped into categories you can reorder. Archived channels stay readable and searchable, and stop accepting new messages.
- Threads
- Any message can become a thread, so a long side-discussion stops burying the transcript it started in.
- Reactions and mentions
- React to anything, mention a person, and see unread and mention counts resolve per channel without a page refresh.
- Direct messages
- One-to-one and group conversations, kept out of the space hierarchy so they cost no space slot and appear in no channel list.
Finding things again
A conversation you cannot find is a conversation you did not have.
- Full-text search
- Across every channel you can see. The visibility check runs inside the query rather than filtering results afterwards, so a private channel you are not in cannot appear even briefly.
- Files
- Upload anything, with per-file and per-organization storage ceilings enforced at upload and reported clearly when one is reached.
- History that paginates
- Message history is keyset-paginated in both directions, so walking back through a busy channel stays fast at any depth.
Talking, not typing
Voice that does not need a separate product.
- Voice channels
- A peer-to-peer mesh for small rooms and a selective forwarding server above the plan threshold, chosen automatically rather than by asking the user which one they want.
- Stages
- Rooms where speaking is a separate permission from connecting, so an audience listens without being able to publish.
- Presence
- Online, away and do-not-disturb, reference-counted per account so a second device does not mark you offline when it disconnects.
Control
The half that a security review asks about.
- Roles and permissions
- A closed permission catalogue shared by the server and every client, resolved through an organization → space → channel scope chain, with per-channel allow and deny overwrites applied last. A deny always wins.
- Audit log
- Every consequential action writes a row: who, what, when, and against which target. Readable by the organization with keyset pagination and real filters.
- Sessions
- See every live session with its device and last-seen, and end any of them. Belonging to several organizations means holding several sessions at once, not being signed out of one to use another.
- Tenant isolation
- Every tenant-scoped route resolves the organization from the session before it reads, and a foreign id answers 404 rather than confirming it exists.
Automation and AI
The work nobody should be doing by hand.
- Webhooks
- Subscribe to eight domain event types, delivered with an HMAC signature and re-vetted against server-side request forgery on every attempt.
- Workflows
- Trigger multi-step automations from a domain event, with a recursion depth limit so a workflow that posts a message cannot re-trigger itself into a loop.
- K Buddy
- Kemble’s assistant, with a per-organization token allowance, a concurrency ceiling, and a sanitiser between it and your content.
Built to be looked at closely
Kemble Work is designed for the organization that will ask how permissions resolve, where the audit rows go, and what happens to data at the boundary between two tenants. Those answers are written down rather than promised.