Channels, posts & threads

truffle. Work, threaded.

Give every channel a job. Start each request as a post. People and connected services work in its thread, approvals happen in context, and the result stays attached to the request.

Create account

Create an account and name your team. Invite the people you work with.

The product

The channel holds the function. The thread holds the job.

Keep recurring work together without mixing separate requests, campaigns, cases, or launches.

product sample — #marketing 12 open posts

Nora · Atlas launch · 09:41

Prepare the Atlas launch for the UK. We need positioning, partner copy, and final approval by Thursday.

top-level post 12 replies

Campaign planner · Connected service · 09:43

The launch brief is ready with audience, message pillars, deliverables, and owners. I kept the work inside this thread.

brief · v1 6 deliverables

Iris · Partnerships · 10:06

Partner copy is attached. Legal needs one change before the launch can move to approved.

Atlas launch · 10:28

The revised copy is approved. The thread now holds the final brief, decision history, owners, and due dates.

status · approved due · Thursday

Channels by function

Set the channel’s job. Start each request clean.

A channel keeps the same team, services, rules, and outputs ready for every new post.

Marketing Campaign briefs, partner inputs, drafts, and approval stay together per launch. One post per campaign

Support A customer issue opens one thread for context, investigation, response, and resolution. One post per case

Hiring Interview notes, scorecards, references, and the hiring decision remain with the candidate. One post per candidate

Incidents Updates, owners, evidence, approvals, and the final review stay in one incident thread. One post per incident

Posts & threads

Many jobs in a channel. No mixed-up context.

The channel is the long-running home for a team function. The post is the boundary for one piece of work.

01 — Post

Name the job

Start a campaign, case, candidate, incident, or launch as a top-level post in the right channel.

02 — Work

Keep every response in its thread

Teammates and approved services add messages to that post's thread without spilling responses into another job.

03 — Decide

Approve with the record in view

Owners make the final call in context. The thread preserves who decided, what changed, and what shipped.

Channel setup

Set up the channel once. Reuse it on every post.

Choose the members, named roles, provider connections, partner services, workflow steps, message outputs, and approvals for that function.

Fig. 01

Post-first channels

The channel groups ongoing work by function. Each top-level post names a separate job.

Fig. 02

Thread boundaries

Replies stay inside their post's thread, so one job cannot silently become part of another.

Fig. 03

Reusable setup

Set up marketing, support, hiring, incident, launch, or custom channels around the work your team repeats.

Fig. 04

Connected services

Assign a provider connection, partner service, or your own service to each step with only the channel access it needs.

Fig. 05

Thread results

Each step returns a message in the thread for the post that started the workflow.

Fig. 06

Reusable roles

Assign who drafts, reviews, approves, or receives the handoff without rebuilding the process for each post.

Fig. 07

Access-aware search

Search messages, threads, and files while channel membership continues to decide what each person can read.

Fig. 08

Scanned attachments

Files are scanned before download and remain attached to the post or thread where the work happened.

Fig. 09

Explicit approvals

Sensitive decisions can require a fresh passkey, and approval authority stays with the designated owner.

Service connections

Connection setup

Once

A team owner selects a provider preset or compatible endpoint, stores one key, and verifies the connection in Account.

Connection options

Guided + custom

Choose a guided provider preset or an HTTPS endpoint your team controls.

Secret sharing

Never

Channel managers assign a named connection to each step without exposing credentials in posts.

Result location

Thread

Every response returns to the post that started the job.

A channel should organize a function. A thread should contain one job from request to approval.

The operating model behind Truffle

Control

Your team stays
in control.

Channel membership limits who can read the work. Connected services use named roles. Sensitive approvals stay with the people assigned to decide.

Channel accesspublic or membership-bound
Post threadsseparate for every request
Credentialskept out of posts
Service rolesexplicitly scoped
Sensitive decisionsowner-approved
Sensitive actionsfresh passkey step-up

Why post-first

A channel for the function. A thread for each job.

Truffle keeps ongoing work visible without turning every request into one continuous group conversation.

Capability	truffle	Flat group chat
Work unit	One top-level post	Another message in the feed
Discussion	A thread for that job	Replies mixed with everything else
Services	Named roles with channel scope	Shared credentials and broad access
Approval	Decision recorded in context	Approval buried in chat
History	Searchable post and thread record	Context reconstructed by hand

Get the app

Use Truffle on web, desktop, or mobile.

Use the web app, install Truffle from a supported browser, or keep up with channels from a phone or tablet.

Web, iPhone & iPad Use Truffle in any modern browser, or add truffle.tech to your iPhone or iPad Home Screen from Safari. Create an account →

Get started

Give recurring work
a place to finish.

Create an account and sign in to your team from the web or an installed app.

Create account Talk to us

truffle · Work, threaded · 2026