Configuring where check-in reports are posted
The report destination controls where compiled answers go after a round closes.
Destination options
| Option | Result |
|---|---|
| Channel only | Summary posts to the Slack, Microsoft Teams, Google Chat, or Discord channel you pick. |
| Dashboard only | Results stay in the Dailybot web app; nothing is pushed to chat. |
| Both | Team sees the rollup in channel and full detail remains in the dashboard. |
Change the destination
- Open Check-ins and select the check-in.
- Open Settings, Report, or Notifications (exact label varies).
- Find Report destination or Post report to.
- Pick a channel, DM, or dashboard-only mode per your UI.
- Ensure Dailybot is in the channel and allowed to post if you use a channel.
- Save.
Multiple destinations
Some setups allow more than one destination (e.g., team channel plus leadership channel). Add each destination the product lists; remove ones you no longer need. If your edition only supports one channel, run a second check-in or use exports for extra audiences.
What the posted report looks like
The chat message is usually a compact summary: who submitted, highlights, blocker lines, and a link to open full responses in Dailybot. Formatting adapts to the platform (blocks in Slack, cards in Teams, etc.). Blocker and critical answers are typically emphasized so they are visible without opening the app.
Long answers may be truncated in chat with a “read more” link to the dashboard. Images and attachments follow your workspace’s platform rules. If you switch from dashboard-only to a channel, the next compiled round is the one that starts posting — past rounds stay in history only.
If reports stop appearing, confirm the bot is still in the channel and that the schedule has run. See Reports not posting when delivery breaks.