Skip to main content

​
Overview

This guide will walk you through the process of inviting Rosy Music Bot to your Discord server, including how to generate an invite link, understand required permissions, and troubleshoot common issues.

​
Step 1: Access Discord Developer Portal

  1. Go to Discord Developer Portal
  2. Log in with your Discord account
  3. Select your bot application from the list

​
Step 2: Navigate to OAuth2

  1. Click on “OAuth2” in the left sidebar
  2. Select “URL Generator” from the submenu

​
Step 3: Configure OAuth2 Scopes

Select the following scopes:
  • bot - Required for bot functionality
  • applications.commands - (Optional) For future slash command support

​
Step 4: Select Bot Permissions

Under “Bot Permissions”, select the required permissions:
  • Read Messages/View Channels - Allows the bot to see channels and read messages
  • Send Messages - Required to respond to commands
  • Embed Links - Needed to display rich embeds with song information
  • Read Message History - For better command interaction handling
  • Connect - Required to join voice channels
  • Speak - Required to play audio
  • Use Voice Activity - For proper voice playback
The minimum required permissions integer is 36700160. You can use this value directly when creating an invite URL.

​
Step 5: Copy the Invite URL

At the bottom of the page, you’ll see a generated URL: 
https://discord.com/api/oauth2/authorize?client_id=YOUR_CLIENT_ID&permissions=36700160&scope=bot
Copy this URL to invite the bot to servers.

​
Required Permissions Breakdown

​
Essential Permissions

These permissions are required for the bot to function:
PermissionWhy It’s Needed
Read Messages/View ChannelsTo see commands sent by users
Send MessagesTo respond to commands and send feedback
Embed LinksTo display song information, queue, and error messages
ConnectTo join voice channels where music will play
SpeakTo play audio in voice channels
These permissions improve the user experience:
PermissionBenefit
Read Message HistoryBetter handling of message-based interactions
Add ReactionsFor future interactive features
Use External EmojisEnhanced embed visuals (if implemented)
Without Connect and Speak permissions, the bot cannot play music. If a voice channel doesn’t grant these permissions, the bot will return an error.

​
Adding to Your Server

​
As a Server Administrator

  1. Open the invite URL in your browser
  2. Select the server from the dropdown menu
  3. Review the requested permissions
  4. Click “Authorize”
  5. Complete the CAPTCHA verification
You must have “Manage Server” permissions to add bots to a Discord server.

​
Verifying the Bot Joined

After authorization:
  1. The bot should appear in your server’s member list
  2. Check the bot’s status (should show as online/idle)
  3. Test with a simple command: r!help

​
Adding to Multiple Servers

The same invite URL can be used for multiple servers:
  1. Share the invite link with other server administrators
  2. Each admin can add the bot to their respective servers
  3. The bot will function independently in each server
Each server (guild) maintains its own music queue and settings. Playing music in one server doesn’t affect other servers.

​
Managing Multiple Guilds

The bot automatically handles multiple servers:
  • Each server has its own queue
  • Volume settings are per-server
  • Commands in one server don’t affect others
  • The bot can play music in multiple servers simultaneously

​
Permission Troubleshooting

​
Bot Can’t See Commands

Issue: Bot doesn’t respond to commandsCause: Missing “Read Messages/View Channels” permissionFix:
  1. Right-click the channel where you’re sending commands
  2. Select “Edit Channel” → “Permissions”
  3. Add the bot’s role
  4. Enable “Read Messages/View Channels”
  5. Save changes

​
Bot Can’t Send Messages

Issue: Bot doesn’t reply to commandsCause: Missing “Send Messages” permissionFix:
  1. Go to Channel Permissions
  2. Find the bot’s role
  3. Enable “Send Messages”
  4. Ensure “Send Messages in Threads” is also enabled if using threads

​
Bot Can’t Join Voice Channel

Issue: Error message “Permisos insuficientes” or “Insufficient permissions”Cause: Missing “Connect” or “Speak” permissions in voice channelFix:
  1. Right-click the voice channel
  2. Select “Edit Channel” → “Permissions”
  3. Add the bot’s role
  4. Enable both “Connect” and “Speak”
  5. Save and try again

​
Embeds Not Displaying

Issue: Messages appear as plain text instead of rich embedsCause: Missing “Embed Links” permissionFix:
  1. Check channel permissions
  2. Enable “Embed Links” for the bot’s role
  3. This permission is also needed in text channels, not just voice

​
Channel-Specific Permissions

​
Restricting Bot Access

To limit which channels the bot can see:
  1. Go to Server Settings → Roles
  2. Find or create the bot’s role
  3. Disable channel access in the role settings
  4. In specific channels, override permissions to allow the bot

​
Voice Channel Restrictions

To control which voice channels the bot can join:
  1. Right-click the voice channel
  2. Edit Channel → Permissions
  3. For bot’s role, set “Connect” to:
    • ✅ Allow (bot can join)
    • ❌ Deny (bot cannot join)
Use permission overrides to create music-only voice channels where the bot has access, while restricting it from other channels.

​
Removing the Bot

If you need to remove the bot from your server:
  1. Go to Server Settings → Members
  2. Find the bot in the member list
  3. Click the three dots next to the bot’s name
  4. Select “Kick” or “Ban”
Removing the bot doesn’t revoke its access token. To fully deauthorize, go to User Settings → Authorized Apps and remove the bot there.

​
Best Practices

Create a Bot Role: Create a dedicated role for the bot with only necessary permissions. This makes permission management easier.
Test Before Sharing: Test the bot in your server first before sharing the invite link with others.
Document Permissions: Keep a list of required permissions for your team to reference when troubleshooting.
Regular Audits: Periodically review bot permissions to ensure they haven’t been accidentally changed.

​
Next Steps

Now that your bot is invited:

Build docs developers (and LLMs) love

Get started for freeTalk to us