Understanding Discord Permissions for Midjourney
Discord has a layered permission system:
- Server-level permissions — Apply to all channels by default
- Channel-level permission overrides — Can allow or deny specific permissions for specific roles in a specific channel
- Bot role permissions — The permissions granted to the Midjourney Bot's role
All three layers must allow the relevant permissions for slash commands to work. A single deny at any layer will block the command.
Step-by-Step Fix
1. Try Using /imagine in a Different Channel
Test the command in a different channel — particularly in the official Midjourney server (discord.gg/midjourney). This tells you whether the issue is channel-specific, server-specific, or account-wide.
- Works in another channel → Channel permission issue (go to step 2)
- Works in official Midjourney server only → Your server's bot permissions are wrong (go to step 3)
- Fails everywhere → Your account may have a restriction (go to step 5)
2. Fix Channel-Level Permissions
- Right-click the problem channel in Discord
- Select Edit Channel
- Go to the Permissions tab
- Scroll through the roles/members listed
- Find Midjourney Bot (or the bot's assigned role) in the list
- Check Use Application Commands:
- If it shows a red X (Denied) → click it to change to green checkmark (Allowed)
- If it is not listed, the server-level default applies — check server settings
- Save changes and test
3. Fix Server-Level Bot Permissions
- Go to Server Settings → Roles
- Find the role assigned to Midjourney Bot
- Scroll to Text Channel Permissions
- Ensure Use Application Commands is toggled on
- Also check Send Messages and View Channels are enabled
- Save changes
4. Check Integrations Settings
- Go to Server Settings → Integrations (for newer Discord)
- Find Midjourney Bot under Bots and Apps
- Review which channels and roles have access
- If a specific channel is excluded, add it to the allowed list
5. Check Your Account and Subscription Status
If the error occurs everywhere, including the official Midjourney server:
- Go to midjourney.com and sign in
- Check your account and subscription status
- Type
/infoto see if the bot responds with your account info - If /info also fails, your account may have been restricted — contact Midjourney support at docs.midjourney.com
6. Re-invite the Midjourney Bot (Last Resort)
If permissions cannot be fixed for an existing bot installation:
- Go to Server Settings → Integrations → Bots and Apps
- Find Midjourney Bot and click Remove
- Re-invite the bot through midjourney.com or the official invite link
- During the invite flow, grant all requested permissions
- Configure channel permissions fresh
Why This Happens
Discord's slash command system requires explicit permission from the server administrator for each bot to use application commands. By default, some Discord server setups restrict slash commands to specific channels or specific roles. If a server was set up before Midjourney Bot was added, or if permissions were changed by an admin, the bot may lack the Application Commands permission even if it is otherwise visible in the server. This is a Discord permission issue, not a Midjourney account issue in most cases.
Common Mistakes to Avoid
- Assuming only your user permissions matter — The bot's own role also needs Use Application Commands permission.
- Only checking server-level permissions and ignoring channel-level overrides — Channel-level denies override server allows. Check both.
- Testing only in your private server and concluding the bot is broken — Always test in the official Midjourney server to confirm the bot is working globally.
- Not checking Integrations settings in newer Discord versions — Discord added a more granular integrations manager that controls which channels and roles can interact with each bot.
- Forgetting that removing and re-inviting the bot resets its permissions — If you re-invite the bot, you must grant permissions again during the invite flow.
Related Issues
- Midjourney bot missing from Discord channel
- Midjourney interaction failed / bot not responding
- Midjourney Discord authorization issues
Q: Why can I type /imagine but the command does not appear in the autocomplete list? If /imagine does not appear in Discord's slash command autocomplete when you type it, the bot either does not have Use Application Commands permission in that channel, or the bot itself is offline. When a bot lacks this permission, Discord hides its commands from the interface entirely rather than showing them greyed out. Check that the Midjourney Bot is online (its status icon in the member list should be green), then verify channel permissions. If the bot is offline, check status.midjourney.com for any active Discord integration incidents.
Q: My subscription is active but I still get 'not allowed to use this command.' Why? An active Midjourney subscription does not automatically grant permission to use commands in every Discord channel — subscription status and Discord channel permissions are separate systems. Your subscription controls what features you can access; Discord permissions control where you can use them. A valid subscription with no channel permissions is just as blocked as having no subscription. Fix the channel permissions using the steps above, then confirm your subscription is active with /info in a working channel.
Q: Can a non-admin user fix Discord bot permissions? No. Only users with the "Manage Channels" or "Administrator" permission in a Discord server can edit channel permissions or bot roles. If you are not an admin, you need to ask your server administrator to grant the Midjourney Bot the necessary permissions. You can diagnose the issue yourself (testing in other channels, checking if commands work in the official Midjourney server), but the actual permission fix requires admin access. Forward this article to your server admin with the specific steps highlighted.
Q: Does removing and re-adding the Midjourney bot reset my generated images? No. Removing the Midjourney Bot from a Discord server and re-adding it does not affect your Midjourney account, subscription, or generated images. Your images are stored in your Midjourney account on midjourney.com, not in the Discord server. The bot is just an interface — removing and re-inviting it only resets its Discord permissions configuration. Your gallery, settings, and subscription remain intact in your midjourney.com account regardless of bot changes.
Q: Is there a way to limit which users in my server can use Midjourney commands? Yes. Discord's Integrations settings allow server administrators to restrict which roles or users can interact with each bot's commands. Go to Server Settings → Integrations → Bots and Apps → Midjourney Bot. From there, you can set which channels allow the bot's commands and which roles have access. This lets you create a dedicated Midjourney channel accessible only to certain roles, keeping image generation organized and preventing casual misuse by other server members.
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.
Related Articles
- Midjourney not generating images
- Midjourney login not working
- Midjourney payment failed
- Midjourney rate limit exceeded
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.