How to Give a Bulk Role to Everyone on Discord

When is it needed?

The most common scenario is this: you enabled autorole after the server had already grown. Autorole is only given to members who join after that point, meaning older members didn't get the role. If you linked channel permissions to a member role, these members won't be able to see the channels. The second common scenario is when you migrate your permission structure to a new role.

This topic in VeyroBot:Discord Reaction Roles (Role Menu) →

Permissions, role hierarchy, and non-privileged roles

• You must actually have the Manage Roles permission on Discord. A bot administrator role granted via the dashboard is not enough for this command; the permission must be present in your Discord role.
• VeyroBot must also have the Manage Roles permission. The role to be distributed must be below the bot's highest role.
• The role must be below your highest role. The server owner is exempt from this rule.
• The role must not grant administrative privileges. A role carrying Administrator, Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Ban Members, Kick Members, or Moderate Members (Timeout) permissions cannot be bulk distributed.
• Other non-distributable roles: @everyone, bot and integration roles, and the verified role given after captcha verification.

You can find detailed information on how the role hierarchy works in our Discord role and permission system article.

Step 1: Prepare the role and channel permissions

First, create or select the role, then configure which permissions will be granted to this role in the channels. Any permission changes made after distribution starts will affect all members simultaneously. Therefore, first assign the role to a test account using /role and check the channels with that account.

Step 2: Run the command

Type /roleall role:@Üye. To also give the role to bots on the server, add include_bots:True; the default value for this option is no.

The command responds instantly, and the distribution continues in the background. The response displays the role to be distributed, the number of members to be scanned, and whether bots are included. If there are members awaiting verification, the number of skipped users is also shown.

Only one bulk distribution can run at a time on a server. A second command will simply stop and display the role and percentage of the ongoing job.

Step 3: Track the progress

A Bulk Role Distribution card will appear in the channel where you ran the command. The card is sent before the first member is processed and updates at most every 15 seconds. The card displays:

• the progress bar and the number of processed members,
• the Given, Skipped, and Failed counts,
• the speed measured while the job is running (roles/min) and the estimated completion time.

The speed depends on Discord's rate limits for assigning roles; on a server with thousands of members, the job can take hours. If the bot restarts in the meantime, the job resumes from where it left off, and the same card continues to update. Once the job is finished, if a moderation log channel is selected, a single summary is written there; individual logs are not created per member.

Which members are skipped?

Stopping the job and self-stopping jobs

• Anyone with the Manage Roles permission can click the Stop button on the card; it is not limited to the person who started the job.
• Stopping is not an undo: roles assigned up to that point remain with the members. The command only adds roles; it does not remove roles from any member. There is no bulk role removal command in VeyroBot.
• Permissions and role hierarchy are rechecked at every turn. If the bot's Manage Roles permission is revoked or if the role is moved above the bot, the job is paused; it resumes from where it left off once the issue is resolved. If the role is deleted, the job is stopped.
• If 20 consecutive requests fail, the job stops due to an error. The card displays the status of the job; for paused jobs or jobs stopped because the role was deleted, the reason is also shown.

To restart a interrupted job, run the /roleall command again. Since members who have already received the role will be skipped, the scan will pass through that part quickly.

Difference from autorole

The two complement each other. First set up the autorole, then distribute the same role to older members using /roleall. This way, both new arrivals and older members see the same channels. Setting up autorole is explained in the welcome message and autorole setup guide.

If the command didn't start or the wrong role was distributed

• Trying to distribute a privileged role. The command will reject it and display the name of the permission in the role. To give such a role to a single person, use /role.
• Leaving the role above the bot. The command won't start. If the role is moved up while the job is running, the job will pause.
• Running the command in a public channel. The response and progress card will appear in that channel for everyone to see. Run the command in an authorized staff channel.
• Thinking the Stop button is an undo. Assigned roles will remain. If you distributed the wrong role, it is often faster to fix the channel permissions of the role rather than removing the role from members.
• Distributing the role without testing. An error in channel permissions will affect all members at once. Try it with a single test account first.

Bulk role or reaction role?

Suitable for: servers that enabled autorole later, migrated channel access to a member role, or want to give everyone a new community role.

Not suitable for: situations where members need to choose their own roles. For preference-based roles like game, notification, or region roles, reaction roles are more appropriate. Privileged roles, on the other hand, are never bulk distributed under any circumstances.

Frequently asked questions

Does /roleall also give the role to new arrivals?

No. The command performs a one-time distribution. Assigning roles to new members continuously is the job of autorole.

How long does the job take?

It depends on Discord's rate limits for role assignment and the number of members who haven't received the role yet. Members who already have the role are skipped quickly since they don't require API requests. The card shows the measured speed and estimated completion time live.

If the bot restarts, will the distribution be interrupted?

No. The job is stored in the database; when the bot starts up, it resumes from where it left off and continues to update the same progress card.

The command says "maximum number of bulk distributions is running." What should I do?

VeyroBot runs a maximum of three bulk distribution jobs simultaneously across all servers. Try the command again in a few minutes.

For a general overview of the feature, you can check the Discord reaction roles page, for all settings the autoroles documentation, and for command details the roleall, setautorole, and role cards.

Last updated: September 26, 2026. The permission rules, skipped members, and progress card behavior in this article have been verified from the bulk role command and distribution engine in the current version of VeyroBot.