Why Your Python Discord Bot Cannot Assign Roles

Running await member.add_roles(role) in discord.py is one of those things that looks completely straightforward until it silently fails or throws a 50013 error – even when you’ve given your bot Administrator privileges. Usually, tracking down the issue comes down to checking three specific layers: Discord's strict role hierarchy, your Developer Portal intents, and how your code handles errors.

The 50013 "Missing Permissions" Exception

The biggest roadblock with role assignment is a super common misconception about how Discord's permissions actually work. Giving your bot "Administrator" or "Manage Roles" is definitely required, sure, but it isn't a magic pass to do whatever it wants. Discord enforces a strict top-down hierarchy, meaning a bot can never assign, remove, or edit a role that sits higher than – or even equal to – its own highest role.

Whenever your code tries to cross that line, Discord's API shuts it down immediately and throws a discord.Forbidden (Error code: 50013) exception, killing the command on the spot.

Requirement 1: Server Role Hierarchy (The Primary Blocker)

To get around this hierarchy block, you’ll need to rearrange how the roles are stacked inside the server itself, and then add a quick safeguard in your code so it checks the order before trying anything.

Correcting Target-Role Placement

Head into Server Settings > Roles inside Discord and find your bot's integration role (that’s the one Discord creates automatically when the bot joins, usually with the same name as the bot). Grab that role and drag it upward until it sits physically above every single role you want the bot to manage.

Programmatically Checking Position in discord.py

Instead of just firing off add_roles blindly and letting a try/except block catch the crash, it's much cleaner to check the role positions beforehand. You can easily compare the target role's spot against the bot's highest role using ctx.me.top_role.position.

if role.position >= ctx.me.top_role.position:
    await ctx.send("Execution blocked: Target role outranks my highest role.")
    return

Requirement 2: Privileged Gateway Intents

If you aren't hitting a 50013 error, yet ctx.guild.get_member(user_id) keeps returning None, the problem is usually that the member isn't sitting in your bot's local cache. To keep that member cache populated, you'll want to turn on the Server Members Intent – though doing a direct API lookup with await ctx.guild.fetch_member(user_id) works too if you'd rather avoid caching.

1. Head over to the Discord Developer Portal. 2.

Click on your application and open up the Bot tab on the left. 3.

Scroll down to Privileged Gateway Intents and toggle on Server Members Intent (so your member cache actually works) and Message Content Intent (so the bot can read the !assign prefix command below). 4. Make sure you also declare those intents right at the top of your Python script before you initialize the bot:

import discord
from discord.ext import commands

intents = discord.Intents.default()
intents.members = True
intents.message_content = True

bot = commands.Bot(command_prefix="!", intents=intents)

Writing a Resilient Role Assignment Command

A solid role assignment command shouldn't just assume everything will go right – it should validate the inputs, check the role hierarchy upfront, and catch API errors gracefully if things still go sideways. Here is a clean, minimal setup you can use to test your configuration:

import discord
from discord.ext import commands

intents = discord.Intents.default()
intents.members = True
intents.message_content = True
bot = commands.Bot(command_prefix="!", intents=intents)

@bot.command(name="assign")
@commands.has_permissions(manage_roles=True)
@commands.bot_has_permissions(manage_roles=True)
async def assign_role(ctx, member: discord.Member, role_id: int):
    # 1. Grab the role object using its integer ID
    role = ctx.guild.get_role(role_id)
    
    if not role:
        await ctx.send(f"Validation failed: Role ID {role_id} not found.")
        return

    # 2. Check the hierarchy before doing anything else
    if role.position >= ctx.me.top_role.position:
        await ctx.send(f"Hierarchy error: I cannot assign '{role.name}' because it outranks me.")
        return

    # 3. Assign the role with proper error handling
    try:
        await member.add_roles(role)
        await ctx.send(f"Success: Assigned '{role.name}' to {member.display_name}.")
    
    except discord.Forbidden:
        await ctx.send("API Rejection: Missing 'Manage Roles' permission or hierarchy conflict.")
    except discord.HTTPException as e:
        await ctx.send(f"Network/API error during assignment: {e}")

bot.run('YOUR_BOT_TOKEN')

Verifying the Fix

To make sure everything is actually working, bring a standard alt or test account into your server to run your tests. Testing on yourself as the server owner can give you false positives because owners automatically bypass a bunch of Discord's normal permission checks.

Run !assign @TestUser [Role_ID] in a test channel to see it in action. If the bot tells you it worked, yet the role never shows up on the test user, check for background conflicts – like another moderation bot instantly stripping the role away, or Discord's membership screening blocking roles until the user accepts the server rules.