Permissions
Understanding and configuring Discord permissions for TeaL;DR.
Required Permissions
TeaL;DR requires specific Discord permissions to function properly. These permissions are requested during bot installation and can be reviewed in your server settings.
Read Messages / View Channels
Purpose: Allows the bot to see channels and read message content for indexing.
Required for:
- Message indexing and search functionality
- Responding to commands in channels
- Generating conversation summaries
Send Messages
Purpose: Enables the bot to send search results and command responses.
Required for:
- Displaying search results
- Sending command responses
- Error messages and notifications
Embed Links
Purpose: Allows the bot to send rich embeds with formatted content.
Required for:
- Formatted search results with metadata
- Statistics displays and analytics
- Rich command responses
Read Message History
Purpose: Allows the bot to access historical messages for indexing.
Required for:
- Initial indexing of existing messages
- Backfilling message history
- Complete search functionality
Use Slash Commands
Purpose: Enables slash command functionality for bot interaction.
Required for:
- All bot commands (/ask, /recap, /stats, etc.)
- Command autocomplete
- Parameter suggestions
Add Reactions
Purpose: Allows the bot to add reaction emojis to messages.
Required for:
- Interactive quiz features
- Feedback collection (👍/👎)
- User engagement features
Managing Permissions
Server-Wide Permissions
To modify bot permissions at the server level:
- Go to Server Settings → Integrations
- Find TeaL;DR in the list
- Click "Manage" to view and modify permissions
- Toggle permissions on or off as needed
Channel-Specific Permissions
To control bot access to specific channels:
- Right-click the channel → Edit Channel
- Go to Permissions tab
- Add TeaL;DR bot role
- Set permissions (allow/deny/inherit)
Role-Based Access
The bot respects Discord's role hierarchy:
- Bot can only index channels it has access to
- Admin commands require user to have Administrator or Manage Server permission
- Bot role position affects what it can access
- Private channels require explicit bot access
Permission Best Practices
✓ Recommended
- • Grant all required permissions during installation
- • Use channel permissions to control access
- • Review bot permissions quarterly
- • Document permission changes
- • Test bot functionality after changes
✗ Avoid
- • Removing required permissions
- • Granting Administrator permission
- • Inconsistent channel permissions
- • Allowing bot in sensitive channels
- • Ignoring permission warnings
Troubleshooting Permissions
Bot Can't See Channels
Check:
- Bot has "View Channels" permission
- Channel isn't private without bot access
- Category permissions aren't blocking access
Commands Not Working
Check:
- Bot has "Use Application Commands" permission
- Bot has "Send Messages" in the channel
- Commands have been registered (wait 5-10 minutes)
Missing Search Results
Check:
- Bot has "Read Message History" permission
- Bot had access when messages were sent
- Channel isn't excluded from indexing
🔒 Security Note
TeaL;DR only requests the minimum permissions required for functionality. The bot never requests Administrator permission and cannot perform moderation actions, delete messages, or manage server settings.