Channel Directory

Browse public and private channels by team, topic, activity, and membership before joining the right conversation. This example brings All channels and My channels together so team members can find the next task without losing context.

It includes representative records such as # product-launch and # customer-feedback. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Channel Directory
Use this template in Figr

Template facts

Screen

Table

Primary action

Create channel

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to create channel while keeping channels, public and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: All channels gives users an obvious place to start.
  • Supporting view: My channels keeps the related context close.
  • Primary action: Create channel stays visible when people need it.
  • First signal: Channels shows a useful value (124).
  • Second signal: Public gives additional context (86).
  • Sample record: # product-launch.
  • Next record: # customer-feedback.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

All channels → My channels → Create channel → Review outcome

Patterns used

Table, All channels, My channels, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to all channels and my channels. People need to distinguish # product-launch from # customer-feedback. Keep channels visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Create channel”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Direct Messages, Message Search, Announcement Composer.

Start from this in Figr

Design a channel directory screen inside our existing product. Use our current components, tokens and content language. Include All channels and My channels views, credible records like # product-launch, and a clear “Create channel” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr