Messaging basics

Channel

A channel is a named destination that groups subscribers who should receive the same realtime events. Other messaging systems may call a similar destination a topic or room.

Also found under: Topic, Room

How it works

Channel design controls how narrowly you can target updates. A channel per project or user avoids sending every event to every client. Channel names are routing identifiers, so a name that looks secret should never replace an access check. Event names distinguish changes inside a channel.

In a Pubb integration

Pubb isolates channel names by application. Public channels are open to clients with the app key; private- and presence- prefixes select channel types that require backend authorization.

Understand channel access

A practical example

Use private-project-42 for a project's authorized viewers, then send task.created and task.completed events through the same channel.