Channel Configuration

ReportFlow can monitor one or more Discord text channels for clockout messages. By specifying exactly which channels to watch, you keep your data clean and prevent accidental processing of off-topic messages in general chat.

Single Channel

Most agencies use one dedicated clockout channel.

Multi-Channel

Large teams can split by model or region.

Role Isolation

Restrict bot access via Discord role permissions.

Selecting a clockout channel

After linking your Discord server, navigate to Settings → Discord → Channels in the ReportFlow dashboard. You will see a list of all text channels the bot can access. Toggle on the channels you want to monitor—typically just one named something like #clockouts or #shift-reports.

Messages posted in unmonitored channels are ignored entirely. This means chatters can continue using general chat, memes, or other channels without triggering the commission engine.

Multi-channel setups

Some large agencies segment clockouts by model or by region. For example, you might have #clockouts-us and #clockouts-eu. ReportFlow supports monitoring multiple channels simultaneously—just toggle on each channel in the dashboard. Commissions and analytics aggregate across all monitored channels while still tracking the source channel for each clockout in the transaction history.

Restricting bot access with Discord roles

The ReportFlow bot only sees channels where its role has "View Channel" permission. In Discord server settings you can assign the bot a role and then remove that role's access to all channels except the ones you want monitored. This provides an extra layer of control beyond the ReportFlow dashboard toggles.

Keep in mind the bot also needs "Read Message History" and "Add Reactions" in the selected channel for full functionality.

Best practices

  • Pin a message with the recommended clockout template in the channel.
  • Use channel permissions to prevent non-chatters from posting in the clockout channel.
  • Avoid renaming the channel frequently—the bot tracks by channel ID, but dashboard labels may lag behind.

Next steps