Create a project channel and add members
Project lead · Set up the workspace
Steps at a glance
1. Decide what the channel is for
Channels are cheap; unfocused channels are expensive. A working pattern for project work is one channel per project — or one channel per phase of a larger project — because it keeps each piece of work's accumulated context clean and separately searchable.
Everything said in a channel becomes the context that agents in that channel draw on. A channel that mixes three projects produces agents that confuse three projects.
2. Choose the channel type and visibility
Two decisions:
Stream or forum. Stream is fast working chat. Forum is async long-form — better for a deliverable that needs considered responses over days, such as analysis findings put to an experienced colleague for review.
Open or private. Open is visible to all community members. Private is hidden and invite-only — and in current versions, invitations to a private channel come from an owner or admin rather than from any member. For anything client-related, default to private and add deliberately, and know who can actually issue the invitation.
Note
Membership is the only content gate in Buzz. There is no second layer of permissions. Who is in the channel is who can read it.
3. Create the channel
Create the channel, giving it a name and description.
Use a description that says what belongs here, not just what the channel is called. It is the only signal a new member gets about scope.
4. Add the people
Add colleagues and specialists as channel members.
Before adding anyone from outside your organisation, check Give an external stakeholder scoped guest access — a full member is not the same thing as a guest.
5. Add the agents
Agents join channels the same way people do. The quickest route is to @mention the agent, which adds it; you can also add it explicitly from the member list.
Add agents deliberately rather than by habit. An agent in a channel can read the channel — that is the whole point, and also the whole risk. See Handle sensitive data where agents are present.
Verified against Buzz v0.5.20 · Updated 2 Sep 2026