Solução de problemas Admin Member

Dailybot can't see my private channel

Dailybot can’t see my private channel

You try to pick a private channel for check-ins, reports, or kudos, but Dailybot’s picker does not list it or posting fails with a not-found style error. Private channels are invisible to apps until the app is a member and until the platform exposes the channel to that integration’s token.

Quick check

Invite the bot — In Slack run /invite @Dailybot inside the private channel. In other platforms, add the bot through that platform’s invite flow for private spaces.
Use an admin account to configure — Channel pickers often require someone who can see the channel to authorize the mapping.
Refresh after invite — Disconnecting and reconnecting is rarely needed; usually reloading the Dailybot web page repopulates lists after invite.
Correct workspace or server — Private channels belong to one workspace; confirm you are configuring the same one Dailybot uses.
Bot not restricted — Some enterprises use channel management policies that block apps from joining certain private channels.

Common causes and fixes

Bot not invited

Private Slack channels, Discord threads, and Teams private channels hide from bots that are not members. Invite Dailybot explicitly, wait until it appears in the member list, then reopen the channel selector in Dailybot. If your template still points at a public channel ID, update it after the invite so sends target the private location.

Platform restrictions on private channels

Google Chat and Teams may require admin approval before a bot can participate in restricted spaces. Slack Connect channels have additional constraints: Dailybot may only work in the home workspace side depending on how the channel is bridged. Read your IT policy: if external guests dominate the channel, automation may be disallowed.

Stale integration cache

After large Slack imports or permission changes, cached channel lists lag. Sign out and back into Dailybot on the web, or use How to disconnect and reconnect your chat platform if invites still do not appear after thirty minutes.

Wrong permission on the configuring user

If you personally cannot see the private channel, Dailybot cannot map it through your session. Ask a channel member who is also a Dailybot admin to perform the setup, or temporarily make you a member.

Archived or frozen channel

Archived Slack channels disappear from active pickers. Unarchive or choose a new channel, then update Dailybot settings.

If none of this worked

Before contacting support, gather:

Platform (Slack, Discord, Google Chat, Teams)
Whether humans can @mention Dailybot successfully in that channel
Screenshot of the member list showing the bot (redact unrelated names if needed)
Workspace or server identifier (non-secret)
Whether the channel is Slack Connect or externally shared
Steps you already tried from this article

Then contact Dailybot support from the Help or Contact options in the product or on the website.