Channels

A channel is a room in the chat space. It is open (any member can read and post) or private (only the members added to it). A DM is a private channel between a few members.

There are two ways a channel comes to exist, and they are signed by different keys:

Org channels

start_workflow("buzz.channel.create", {
  "space_uuid": "<space uuid>",
  "name": "support",
  "visibility": "open",
  "about": "Questions about your orders"
})

data.buzz.channel.list is also what the chat page reads for an end user: the channels of their app, open channels, in their workspace. It returns the relay URL and the relay public key the page verifies channel metadata with.

data.buzz.member.channels reads the relay's own signed member lists. It never lists DMs, and it cannot see a private channel the owner key is not in, such as one a member created on the chat page.

Adding an actor to a channel with buzz.channel.set-member makes it a listener there: it answers mentions and DMs in that channel. To make it answer every message of a channel, list the channel in its triggers. See Actors in chat.

Channels your members run

When the space allows it, end users manage channels themselves from the chat page. Each action is an entry point on your identity app that wraps one workflow, and each is signed with the person's own chat key.

To let members create channels, set features.member_channel_create to true in the theme and publish it. See Theme and customization.

The relay applies its own channel rules, and a refusal comes back as channel_command_refused: <relay code>:

• only a channel's owner and admins can rename it, describe it or archive it; any member can set the topic;
• private channels cannot be joined, only added to;
• the last owner cannot leave.

On top of that, the platform refuses a member who tries to give someone an elevated channel role.

Private channels

A private channel starts with its members. An organization creates one with buzz.channel.create, visibility: "private" and member_uuids. A member creates one on the chat page and picks the people to add; that runs buzz.channel.create-as-member with the same two inputs. After that, people are added with buzz.channel.set-member (organization) or the invite action (member).

Relay owners and admins are not automatically members of a private channel. If your organization needs to read one, add a member to it rather than expecting admin access.

Ask your AI assistant

List the channels of my chat space with data.buzz.channel.list, including archived ones.

Create an open channel called "announcements" in my chat space. Show me the buzz.channel.create inputs and wait for my confirmation.

Which channels is the member "<name>" in? Use data.buzz.member.list to find them, then data.buzz.member.channels.

Let my end users create their own channels: update the theme so member_channel_create is true, save it as a draft and publish after I confirm.

For AI agents