Understanding Discord permissions for Dailybot
When you install Dailybot on Discord, Discord asks you to approve a list of permissions. This article explains why Dailybot needs each one and what the bot does (and does not) do with that access, so server admins can install the app with confidence.
What Dailybot uses each permission for
Channel permissions
Dailybot needs channel access to post daily check-in reports in the channels you configure on the dashboard. Configuration is explicit: the bot only joins or posts in channels you set up beforehand in Dailybot’s settings; it does not auto-join channels in your server.
The channel permission is also used to receive commands – for example when someone types @dailybot in a channel or runs a slash command from one.
Member permissions (for private check-ins)
For private daily check-ins, Dailybot needs permission to send direct messages to members. This is how the bot asks check-in questions one-on-one, instead of in a public channel.
What Dailybot does not do
- Dailybot does not read or store messages in public or private channels. The channel permission is used only to (a) receive commands directed at the bot and (b) post reports to configured channels.
- Dailybot does not access private conversations between users. When the bot has member-level permission, it only engages with messages directly related to Dailybot’s own activity (check-in answers, commands, replies to bot prompts).
Quick check before installing
- You are a server admin. Only Discord admins (or someone with Manage Server) can authorize the bot.
- You have decided which channels Dailybot will post in. Configure them in the Dailybot dashboard before or after the install; the bot will not pick channels on its own.
- You understand that private check-ins use DMs. If your team prefers channel-only check-ins, you do not have to enable the private check-in flow.