Why Can't My Discord Bot Pin Messages or Create Emoji Anymore? (Feb 2026 Permission Changes)

Your bot lost the ability to pin messages, create emoji, or manage events because Discord split those abilities out of older catch-all permissions in early 2026. The fix is to grant the new granular permissions ("Pin Messages," "Create Expressions," "Manage Expressions," "Create Events," "Manage Events") directly to your bot's role. Nothing is broken with your bot itself. Its old permission is still on, but that permission no longer covers everything it used to.

If your bot suddenly started failing at small jobs it handled fine last month, this is almost certainly why. Below is exactly what changed, how to check your bot's role, and what to flip back on.

What suddenly broke for many bots in 2026

The classic complaint reads something like this: "My bot has Manage Messages, but it can't pin anymore." Or: "My leveling bot used to add level-up emoji and now throws a permissions error." Or: "Scheduled event reminders stopped posting."

The common thread is that the bot still has the permission it always had. Server owners check the role, see the toggle is still green, and assume the bot is buggy. It isn't. Discord changed what those toggles actually grant.

When Discord splits a broad permission into smaller ones, existing roles keep the broad permission but do not automatically receive the new narrow permissions. So the moment the split happened, every bot relying on the old behavior lost the part that got carved out, while looking like nothing changed.

The permissions Discord split apart (Pin, Expressions, Events)

Three areas got broken into finer-grained controls. Here is what moved where.

Pinning messages

Pinning and unpinning used to ride along with Manage Messages. That permission did a lot: deleting other people's messages, removing reactions, and pinning. Discord separated Pin Messages into its own permission so server owners can let a bot pin announcements without also handing it the power to delete everyone's messages.

The side effect: a bot with Manage Messages but without the new Pin Messages permission can no longer pin. The capability it relied on quietly left the permission it was attached to.

Creating and managing emoji, stickers, and soundboard sounds

Discord groups emoji, stickers, and soundboard sounds under the umbrella term Expressions. The old single permission, Manage Emojis and Stickers (later "Manage Expressions"), got split into two:

• Create Expressions lets a role add new emoji, stickers, and soundboard sounds.
• Manage Expressions lets a role edit or delete existing ones, including ones it didn't create.

A bot that used to "Manage Emojis and Stickers" to upload a new emoji now needs Create Expressions specifically. Having only Manage Expressions is not enough to add something new, which catches a lot of people off guard.

Scheduled events

Events followed the same pattern. Manage Events was one permission. It split into:

• Create Events to schedule new events.
• Manage Events to edit, move, or cancel existing ones.

Event bots, raid schedulers, and community-calendar tools that create events on a timer need Create Events now, not just Manage Events.

Why your bot lost abilities it used to have

This is the part that trips everyone up, so it's worth being precise.

Discord permissions are stored as a bitfield: a long number where each bit is one permission. When Discord introduces a new permission, it adds a new bit. Existing roles have that new bit set to off by default, because the role was created before the bit existed.

So when "Pin Messages" became its own bit, your bot's role had it off from day one of the change. The Manage Messages bit your bot already had stayed on, which is why the toggle still looks correct. The pinning behavior simply moved to a bit your bot was never granted.

This is also why reinstalling the bot, kicking and re-inviting it, or restarting it does nothing. The permission gap is on the role, not in the bot's code. You have to grant the new permissions on the role the bot uses. If you're seeing a broader pattern of features failing, our guide on why your Discord bot stopped working in 2026 walks through the other common causes too.

How to grant the new granular permissions

You can fix this in a couple of minutes. Here's the reliable path.

Step 1: Find the bot's role

Open Server Settings → Roles. Most bots get a role named after the bot when they're invited (for example, a role called "PeakBot"). That's the role you'll edit. If your bot has multiple roles, you can grant the permission on any role the bot holds, since permissions are additive.

Step 2: Open the role's permissions

Click the bot's role, then open the Permissions tab. You'll see the full permission list with the new entries already present: Pin Messages, Create Expressions, Manage Expressions, Create Events, and Manage Events.

Step 3: Toggle on only what the bot needs

Turn on the specific permissions that match what broke:

• Bot can't pin? Enable Pin Messages.
• Bot can't add emoji, stickers, or sounds? Enable Create Expressions (add Manage Expressions if it also edits or removes existing ones).
• Bot can't schedule events? Enable Create Events (add Manage Events if it also edits or cancels them).

Grant the narrow permission rather than a broad one. There's no reason to hand a pin-only bot full Manage Messages just to make pinning work again.

Step 4: Save and check channel-level overrides

Server-wide role permissions can be overridden per channel. If a bot pins fine in one channel but not another, open that channel's settings, go to Permissions, find the bot's role, and make sure the new permission isn't set to a red X there. A channel override always beats the server-wide setting.

Step 5: Test the exact action that failed

Trigger the same command or automation that broke. If it works, you're done. If it still fails in one channel only, that channel has an override (revisit Step 4). For a complete reference on how role and channel permissions interact, see our full Discord permissions guide for 2026.

Checking a bot's role for the right toggles

A quick audit checklist for any bot that does more than chat:

• Pinning: Pin Messages on (separate from Manage Messages now).
• Emoji / stickers / sounds: Create Expressions on; add Manage Expressions only if it edits existing ones.
• Events: Create Events on; add Manage Events only if it edits or cancels them.
• Reactions, deletes, reaction roles: still under Manage Messages and Add Reactions, unchanged by these splits.
• Channel overrides: confirm no red X on the bot's role in the specific channels where it operates.

If you're setting up a bot from scratch and want to know the minimum it actually needs, our breakdown of what permissions to give a Discord bot covers the safe baseline so you don't over-grant.

What server owners should audit now

The pin, expressions, and events splits are the ones generating support tickets, but a few related habits are worth checking while you're in there:

• Re-grant after any future split. Discord has repeatedly broken broad permissions into narrow ones. Each time, your existing roles keep the old bit and miss the new one. Treat "a feature silently stopped" as a permissions audit, not a bug report.
• Avoid blanket Administrator on bots. It's tempting to give a bot Administrator so you never see a permissions error. Don't. Administrator overrides everything, including channel restrictions, and makes a compromised bot far more dangerous. Grant specific permissions instead.
• Watch role position. A bot can only manage roles, emoji, and members below its own role in the list. If you reorganized roles recently, the bot may technically have the permission but sit too low to use it.
• Check both server and channel scope. The most confusing failures are "works here, not there," which almost always means a channel override.

If managing several bots' permissions has become a chore, that's part of why all-in-one bots exist. Running one bot for moderation, XP and leveling, tickets, welcome messages, and reaction roles means one role to audit instead of five.

Keeping bot permissions correct going forward

The single most useful habit: when a bot feature stops working, check the bot's role permissions and channel overrides first, before assuming the bot is broken. In the vast majority of 2026 cases, it's a permission that got split or an override that got changed.

Consolidating bots also reduces the surface area. Every extra bot is another role to keep correct, another set of permissions to re-grant when Discord changes something. PeakBot is built to replace MEE6, Carl-bot, Dyno, and TidyCord with one bot, which means one role to maintain.

To be fair to the alternatives: Dyno is dependable for straightforward auto-moderation, Carl-bot's reaction-role and tag system is genuinely deep, and MEE6 is the name most newcomers already know. Each does its core job well. Where PeakBot stands out is being a free, all-in-one option with context-aware AI moderation that reads message intent instead of matching a fixed keyword list, plus an AI Server Builder that generates a full custom server, channels, roles, categories, permissions, and automations, from a plain-English description in under 60 seconds.

PeakBot ships 30+ features free with no time limit and no trial. Pro is $8.25/month per server (or $69/year), compared with MEE6 premium at $11.95/mo and Carl-bot premium at $7.99/mo. It currently powers 500+ Discord communities. You can see the full free feature list on the features page or compare it side by side with your current bots on the comparison page.

FAQ

Why can't my Discord bot pin messages anymore in 2026?

Discord split Pin Messages out of the Manage Messages permission. Your bot still has Manage Messages, but pinning now lives in a separate permission that existing roles didn't automatically receive. Enable Pin Messages on the bot's role to fix it.

How do I let my bot create emoji again?

The old "Manage Emojis and Stickers" permission was split into Create Expressions (for adding new emoji, stickers, and sounds) and Manage Expressions (for editing existing ones). Turn on Create Expressions for the bot's role. Manage Expressions alone won't allow uploads.

Did Discord change event permissions too?

Yes. Manage Events was split into Create Events and Manage Events. A bot that schedules new events needs Create Events; it only needs Manage Events if it also edits or cancels existing ones.

Will reinstalling or re-inviting the bot fix it?

No. The gap is on the role's permissions, not in the bot's code, so kicking, re-inviting, or restarting the bot changes nothing. You have to grant the new granular permissions on the role the bot uses.

Should I just give the bot Administrator to avoid this?

It's not recommended. Administrator overrides every restriction, including channel-level limits, and makes a compromised or misbehaving bot far more dangerous. Grant the specific permissions the bot needs instead, like Pin Messages or Create Expressions.

My bot can pin in one channel but not another. Why?

That's a channel-level permission override. A channel can set the bot's role permission to a red X, which beats the server-wide setting. Open that channel's settings, go to Permissions, find the bot's role, and clear the override.