Docs/Channels/Channel Settings

Channel Settings

Configure visibility, categories, and routing

Each channel has a range of settings that control how feedback is collected, where it's routed, and how it appears to submitters.

Basic settings

  • Name — The display name shown in the dashboard and on the feedback form header
  • Slug — The URL-friendly identifier used in the public form URL (e.g., bug-reports)
  • Type — External (open to end-users) or Internal (for team members only)
  • Status — Active or paused. Paused channels show a message to visitors that feedback is not currently accepted

Category tags

Category tags define what types of feedback this channel collects. When a submitter starts a conversation, they can optionally select a category. The AI uses the selected category to ask more relevant follow-up questions.

Tags are free-form — you type them in as a comma-separated list (e.g. Bug, Feature, UX, General). Add or remove tags at any time; whatever tags are saved will appear as options on the feedback form. There are no fixed or predefined categories.

Visibility and access

Channels can be configured with two visibility modes:

  • Public — Anyone with the link can submit feedback. No authentication required.
  • Private — Access is restricted to people who have the private link. The access code is included as a ?code= URL parameter — visitors who arrive without a valid link see a closed-access message and cannot proceed.
Tip
Use private channels for internal feedback collection or when you want to limit access to specific user groups like beta testers.

Theme

Each channel has its own theme — either dark or light. This controls the appearance of the public feedback form and is chosen when the channel is created. The theme setting is independent of your dashboard theme preference.

Issue tracker routing

Each channel settings page shows a tab for every issue tracker you have connected. Configure the relevant tab to control where issues end up:

  • Linear tab — Select the Linear team and optionally a project. Also where you set the feedback mode (Single, Auto-Split, or Split & Review) for this channel.
  • GitHub tab — Select the repository that issues from this channel are pushed to. Appears when GitHub is connected.
  • Jira tab — Select the Jira project and default issue type. Appears when Jira is connected.

If no external tracker is configured, issues stay in Flowback's native issue system. You can route feedback from different channels to different trackers or teams — for example, bug reports to Engineering and feature requests to Product.

Slack channel

If Slack is connected, you can assign a specific Slack channel for this feedback channel's notifications. When new submissions come in, notifications are posted to the assigned Slack channel. If no channel-specific Slack channel is set, notifications use the workspace default.