When you transfer ownership of a Discord server to another user, all bots and integrations that required your original owner permissions may stop working. The new owner must manually reassign roles and permissions for each bot, which can break automated moderation, music playback, and logging features. This article explains how to transfer server ownership correctly so bots retain their full functionality. You will learn the exact steps to prepare roles, transfer ownership, and verify bot access after the change.
Key Takeaways: Transfer Server Ownership Without Bot Disruption
- Server Settings > Roles > Create a custom bot role: Assign all required permissions to a dedicated role before transferring ownership.
- Server Settings > Members > Transfer Ownership: The new owner must be a server member with at least the administrator permission for 24 hours before the transfer.
- Server Settings > Roles > Reorder role hierarchy: Move the bot role above the new owner’s role to prevent permission conflicts.
Why Bot Permissions Break After Ownership Transfer
When you transfer server ownership, the original owner loses all permissions except those granted by roles. Bots that were authorized by the original owner’s user ID or by the owner-level “Manage Server” permission may lose access to channels, voice regions, and moderation commands. Discord’s permission system treats the server owner as a special entity that bypasses role hierarchy. Once that owner is replaced, bots that relied on the owner’s implicit permissions no longer have those privileges. The new owner must explicitly grant the same permissions to the bots through roles. If you do not prepare roles beforehand, bots will show errors like “Missing Permissions” or “Bot cannot execute this action.”
Steps to Transfer Discord Server Ownership Without Losing Bot Permissions
- Create a dedicated bot role with all necessary permissions
Open Server Settings > Roles. Click “Create Role” and name it something like “Bot Admin” or “Bot Permissions.” Enable all permissions the bot needs: Read Messages, Send Messages, Manage Messages, Kick Members, Ban Members, Manage Channels, Manage Roles, and any other specific permissions required by your bots. Do not assign this role to any human user. Click “Save Changes.” - Assign the bot role to each bot
Go to Server Settings > Roles. Click the role you just created. Under “Manage Members,” add each bot by selecting its name from the dropdown. If you have many bots, repeat this step for each one. Ensure every bot has the role assigned before proceeding. - Verify bot permissions in all channels
Right-click each text and voice channel and select “Edit Channel.” Go to the “Permissions” tab. Click “Advanced Permissions” and confirm that the bot role has the green checkmark for all required permissions. If a channel has custom overrides that conflict, adjust them now. This step prevents permission gaps after the transfer. - Ensure the new owner has been a server member for at least 24 hours
Discord requires the new owner to have joined the server at least 24 hours before you can transfer ownership. If the new owner is a recent addition, wait the full 24 hours. Also confirm the new owner has the “Administrator” permission or a role with all necessary permissions to manage the server. - Transfer ownership to the new user
Go to Server Settings > Members. Find the new owner in the member list. Click the three-dot menu next to their name and select “Transfer Ownership.” Confirm the transfer in the dialog that appears. Discord will ask for your password or two-factor authentication code. Enter it to complete the transfer. - Have the new owner reassign bot roles if needed
After the transfer, the new owner must verify that all bots still have their roles. Go to Server Settings > Roles. Check that the bot role is still assigned to each bot. If any bot lost its role, click the bot role and add the bot again. The new owner can also create a new role with the same permissions if the original role was accidentally deleted during the transfer. - Test each bot’s core commands
Ask the new owner to run a few commands from each bot: a moderation command, a music play command, and a logging command. Confirm that no “Missing Permissions” errors appear. If a bot fails, check its role permissions again and ensure the role is above the new owner’s role in the role hierarchy.
Common Mistakes That Break Bot Permissions After Ownership Transfer
Bot role is below the new owner’s role in the hierarchy
Discord uses role hierarchy to determine which roles can modify others. If the bot role is positioned below the new owner’s highest role, the bot cannot perform actions that require modifying members or messages that the new owner has access to. Move the bot role above the new owner’s role by dragging it in Server Settings > Roles. The bot role should be at the top of the role list, just below the @everyone role.
Bots were authorized using the original owner’s OAuth2 token
Some bots require a user token or OAuth2 authorization link that was generated by the original owner. After ownership transfer, the original owner’s token is no longer valid for server management. Re-authorize the bot using the new owner’s Discord account. Visit the bot’s website or use the bot’s invite link again. The new owner must click “Authorize” and select the server. This step applies mainly to custom bots or self-hosted bots that use user tokens.
Channel-specific permissions were set for the original owner only
If you previously added the original owner as a channel-specific override with custom permissions, those overrides are removed when ownership changes. The new owner must manually add the bot role to each channel’s permission list. Go to each channel, edit permissions, and add the bot role with the required permissions. This is especially important for private channels where the bot needs access.
Bots that require “Manage Server” permission lose access
The “Manage Server” permission is automatically granted to the server owner. After transfer, the new owner has this permission, but bots that were relying on the original owner’s implicit “Manage Server” access no longer have it. Ensure the bot role explicitly includes the “Manage Server” permission in the role settings. Without it, bots cannot change server settings like the server name, verification level, or welcome screen.
Discord Permission Levels: Owner vs Administrator vs Custom Role
| Item | Server Owner | Administrator Role | Custom Bot Role |
|---|---|---|---|
| Permission source | Automatic by ownership | Role with Administrator toggle | Custom role with specific permissions |
| Survives ownership transfer | No (transfers to new owner) | Yes (if role is assigned) | Yes (if role is assigned) |
| Bypasses role hierarchy | Yes | Yes | No |
| Can be assigned to bots | No | Yes (but not recommended) | Yes (recommended) |
Transferring Discord server ownership does not have to break bot permissions. The key is to create a dedicated bot role with all required permissions before the transfer. Assign that role to every bot and verify channel-specific overrides. After the transfer, the new owner should test each bot immediately. If a bot fails, re-authorize it using the new owner’s account. This approach preserves all bot functionality and avoids manual permission fixes later.