DISCORD SETUP
Pick a topic below. Each one stands on its own — work through them in any order.
Before you start
A Discord server is a chat space. It is not a game server. It has no game running in it. It is a place with channels (rooms for text, voice and video) where your community talks. Your game servers and your Discord server are separate things, and you can run either one without the other.
What you need: a Discord account, and Discord open, either the desktop app or discord.com in a browser. Discord's own create steps are written for the desktop app or the browser, and nothing we found covers the phone app. Some things below (templates, Onboarding setup) Discord says work only on the computer. If your screen looks different from the words here, go by the words on your screen.
Two decisions to think about first. Neither locks you in.
- What is the server for? A few friends, or a larger community. Discord asks this during setup.
- Standard or Community? Community mode adds moderator tools and some rules you must follow. You do not need it to have a working server. A later section explains it so you can decide on purpose.
First, we are going to open Discord and create the server.
Start here.
Create the server
These steps all happen inside Discord, on your computer. First, we are going to find the button that starts a new server.
- Find Add a Server.
1. Look at the left sidebar. It lists your servers.
2. Find the + (plus sign) button. Hovering over it or clicking it says Add a Server. Discord says it can be hidden if you are in a lot of servers, and that you scroll down the server list to find it.
Next step: we open the create pop-up. - Choose Create My Own.
1. Click the +. A pop-up opens with the heading Create Your Server and a short note saying this is where you and your friends hang out. It has the choices Create My Own and a templates choice (start from a template). At the bottom is a box that says Already have an invite code? with a Join a Server button. Use that box only if you are joining someone else's server.
2. Choose Create My Own. This is the plain, empty server. Templates are covered in the next section, and you can skip them for now.
Next step: we say who the server is for. - Say who the server is for.
1. Discord offers to guide you through setup for a friends server or a community server, and says you can skip it if you are unsure. Your screen words the two choices For me and my friends and For a club or community.
2. Pick the one that fits. Example: a group of six people who play together every week is For me and my friends. A server for a streamer's viewers is For a club or community.
3. Discord's pages do not say what this choice changes. One third-party guide (not Discord, May 2026) says it only changes a few default permissions and you can adjust them later. We could not confirm that. What Discord does say is that a friends server can opt in to Community at any time in the server settings, so you are not stuck.
Next step: we name the server. - Name it and add a picture, then create it.
You land on a Create a server screen with a box for the server name and a spot to upload a photo.
1. Type a server name. Pick a name that tells a stranger what the place is for. Example: Maple Street Gamers tells people more than Server 1 does. This is only an example. Use your own.
2. Optional: add an icon (the small picture next to your server's name). Choose an image file from your device. Discord says the minimum size is 128 by 128 pixels (a pixel is one dot of the picture), and that if you crop a big image, you should crop it in multiples of 128. Example: a 512 by 512 picture is fine, because 512 is 4 times 128.
3. Click Create. (A Back button sits on the other side if you want to change your last choice.)
4. Discord says the name and icon can be changed later, so you do not need to get them perfect now.
Next step: you decide whether to use a template, then whether to turn on Community.
If you see your server's name in the list, it worked. We have not seen what Discord shows right after this, so go by your screen.
Start blank or from a template
A template copies someone else's layout. It saves time if you want a ready-made set of channels, but you then have to rename and delete what you do not need. If you are brand new, starting blank is fine. Planning your channels is the job of the Design & Structure topic, which is the next tab.
First, we are going to look at what a template does and does not copy, so you can choose.
What a template copies, what it does not, and how to make your own
- What it copies. Discord's template page says a template clones categories, channels, roles and permissions. A category is a labeled group of channels. A role is a label that gives people permissions.
- What it does not copy. The same page says Community-only channel types (Forum, Announcement and Stage) are not carried over. We read nothing about members or messages, so do not assume they are included.
- Using one. Discord says you can preview a template before you create a server from it, and rename the server and upload a new picture from the preview window. Then you choose Create.
- Which templates Discord offers. Discord's pages do not list them. We have not seen the template screen, so we cannot tell you what is in each one. Read the descriptions on screen before you pick.
- Making your own template later. You need to be the server owner or have the Manage Server permission. Open Server Settings (the dropdown next to the server name, or right-click the server name), then the Server Template tab, type a name and a short description, and press Generate Template. Then press Copy to share the link. Discord says this works on the desktop app and the browser, not the phone app.
- Templates do not update by themselves. After you change your server, go back to Server Template and press Sync Template. To remove a template link, use Delete Template on the same tab. If the creator deletes it, the link stops working.
Next step: we decide whether this server should be a Community server.
This one changes your server's settings. Read it before you click.
Community or standard server?
A Community server is a server with extra tools for running a larger group. A standard server is just the server you made above. Discord says a friends server can opt in to Community at any time, and that you can switch it off again, so you can wait.
Our advice: if the server is just you and your friends, skip this section for now. Come back when you want the tools below.
Discord's page on this is marked "2 years ago" and is the newest official one we found. We could not find a 2026 Discord page, so check each screen as you go. First, we are going to look at what Community gives you and what it asks of you.
What Community adds (from Discord's pages)
- Server Insights. Numbers about how your server is doing.
- Raid Protection. Discord's Onboarding page says it uses machine learning to spot a likely join-raid (a flood of fake accounts joining at once), alerts you, and can require a CAPTCHA (a "prove you are human" check) for new joiners for the next hour. Alerts are set up in Server Settings, Safety Setup, Raid Protection.
- Rules and Onboarding. A rules channel, and Community Onboarding: new members answer a few questions to pick their own roles and channels. The next dropdown explains it.
- Announcement channels. Special channels that other servers can follow. Also forum channels, which standard servers do not have.
- Updates from Discord sent to a channel only your moderators see.
- Server Discovery. Discord's page says this is currently limited to servers with more than 1000 members, plus Partnered and Verified servers.
- Never-expiring invite links. Discord's help says only Community servers can make them. But the Expire After list on a standard server we checked still showed Never as a choice. We saw it again on a server that had Community turned on and then off. We did not pick it, so we do not know whether the link really never expires. Check the invite's expiry after you make it.
Discord says Community does not mean anyone can find or join your server. People still need an invite link. About the Welcome Screen: Discord's enable page says you can no longer edit it on a Community server, and recommends Community Onboarding instead.
What Community asks of you (the requirements)
Discord's enable page says you must have all of these on:
- A verification level that needs a verified email. A verification level is the check a new member must pass before they can chat. This one means they have a verified email on their Discord account. Discord notes it does not apply to people who have been given a role.
- The Explicit Media Content Filter set to scan media content from all members. Careful: Discord says this scans all media sent in the server and deletes anything it thinks is explicit. It also says channels with explicit content must carry an age-restricted label.
- A Rules or Guidelines Channel. A channel where your rules are clearly posted. Example name: #rules.
- A Community Updates/Moderators Channel. The channel where Discord sends announcements for your admins and moderators. Example name: #mod-updates. These are only example names. Use your own.
- Your server must follow Discord's Community Guidelines.
Setup either creates these two channels for you or lets you pick existing ones. On our test server we let it create them. It made a channel called rules and a locked channel called moderator-only.
The three setup screens, as we saw them
We walked through Community setup on a test server. Setup is a window titled Let's set up your Community Server. with three steps down the left side: Safety checks, Setting up the basics and Finishing touches.
- 1. Safety checks (screen title Keep your community safe). It says Community servers must have two moderation settings on, each with a checkbox: Verified email required. (members need a verified email before they can send messages; it does not apply to members with roles) and Scan media content from all members. under the heading Explicit Media Content Filter (Discord scans and deletes media that contains explicit content, except in age-restricted channels).
- 2. Setting up the basics (screen title Set up the basics). Two dropdowns: Rules or Guidelines Channel and Community Updates Channel. Both start on Create one for me, which makes the channel for you. You can pick an existing channel instead. Discord's note for the updates channel recommends a role-restricted channel, because the updates can include sensitive information.
- 3. Finishing touches. A Safe settings section with two ticked items: Set default settings to Mentions Only (default notification setting for members) and Disable risky permissions for @everyone. The screen lists what that disables for everyone: Create Emoji, Create Events and Mention @everyone. It also lists permissions already off: Administrator, Kick Members, Ban Members, Manage Server, Manage Channels, Manage Roles, Manage Messages, Manage Emoji, Manage Events, Moderate Members and Manage Official Messages. Below that is a Follow the rules section. It says that by setting your server as a Community Server you agree that it complies with Discord's Community Server Guidelines (linked), and it has a checkbox labeled I agree and understand. Tick that, and the Finish Setup button becomes active. Read the linked guidelines first. Ticking the box is you agreeing to them for your server.
So turning Community on is not only a label. It can change notification defaults and what regular members are allowed to do. Read screen 3 before you press Finish Setup.
What you get after Finish Setup, as we saw it
On our test server, right after Finish Setup:
- Two new channels, marked NEW: rules (a rules-style channel) and moderator-only (a locked text channel). Both appeared under Uncategorized, not inside a category. Your normal channels were still there.
- The sidebar changed. Enable Community is gone. In its place are Community Overview, Onboarding and Server Insights.
- Community Overview has the title Community Settings and a banner, Your server is now a Community Server!, with three buttons: Set up Onboarding, Apply for Discovery and Check Server Insights.
- Below the banner: Rules or guidelines channel (ours showed rules), Community Updates Channel (ours showed moderator-only), Safety Notifications Channel (ours showed Select..., meaning not chosen yet), Server Primary Language (English) and Server Description.
- At the bottom, a red Disable Community button. Discord's text under it: "This will remove specific features for Community Servers, like Server Discovery and Server Insights."
We then pressed Disable Community on the test server. Both channels stayed: moderator-only kept its lock icon, and rules stayed but now shows a plain # channel icon instead of the rules-style one. Both were still under Uncategorized. After that, the sidebar went back to normal and showed Enable Community again, with no Community Overview, Onboarding or Server Insights. Setup's permission changes did not revert: Create Events for @everyone was still off after we disabled Community, so turn it back on yourself in Roles > @everyone > Permissions if you want it. We checked only that one permission; we did not check Mentions Only or the others. So turning Community off does not delete the channels setup made for you. Delete them yourself if you do not want them.
What are the questions new members answer? (Community Onboarding)
Community Onboarding is a short set of questions a new member answers when they join. Their answers give them roles and show them the channels you chose. It is optional. Discord's Onboarding page (marked "3 years ago") says:
- Where: Server Settings, then Onboarding. You need the Manage Server and Manage Roles permissions, or Administrator. Discord says admins can only set it up on the desktop.
- Default Channels: the channels every new member sees. You must pick at least 7, and at least 5 of them must let @everyone (every member) view and send messages.
- Customization Questions: you write a question and some answers, and each answer gives roles and/or channels. Example: the question What would you like to do here? with answers Play games and Chat, where each answer unlocks different channels. These words are only an example.
- Question options: Ask before a member joins, Allow multiple answers and Make Required. There is also a Preview button to test it.
We have not tried it. Roles and channels are explained in the next topics.
- Turn Community on (only if you decided yes).
1. Click your server's name in the upper left corner, then choose Server Settings.
2. In the left sidebar, scroll down to Enable Community and select it.
3. Click Get Started and go through the steps. Read the part where Discord asks you to confirm you understand the Community rules.
4. Press Finish Setup.
Afterward, you change Community settings in Server Settings under Community Overview. There you can change the rules channel, the updates channel, the safety notifications channel, the primary language and the description. The dropdown above shows the whole screen.
Next step: if you change your mind, we show how to turn it off. - Turn Community off (if you want to go back).
1. Open Server Settings, then Community Overview.
2. Scroll to the bottom and press the red Disable Community button. Discord says it removes features like Server Discovery and Server Insights.
3. If Discord asks you to confirm, do so. Discord's help page says you can turn Community back on later.
Discord's page does not say what happens to your Announcement and Forum channels, so write down what you have in them first. On our test server it kept the rules and moderator-only channels that setup had created (rules became a plain text channel). The safe settings from screen 3 are not all put back: Create Events for @everyone stayed off. We did not check Mentions Only or the other permissions, so look at them yourself. Go by what your screen says.
Next step: we invite people in.
Invite people
An invite is a link. Discord says the only way anyone can get into your server is through an invite link, so it is the key to your server. These steps happen inside Discord, in a channel of your server. First, we are going to make one invite link.
- Create an invite.
1. Click your server's name at the top of the channel list, then choose Invite to Server. (Discord's help page also describes hovering over the right-hand side of a channel and choosing Create Invite. We have confirmed only the menu route on a real screen.)
2. A window opens titled Invite friends to and your server's name. Under it, Recipients will land in shows which channel new people arrive in. Below that are a Search for friends box and a list of your friends, each with an Invite button, which sends them the invite as a message. At the bottom, Or, send a server invite link to a friend shows the link with a Copy button.
3. If the channel is private, the window warns that only select members and roles can view it. Someone who joins through that link lands in a channel they cannot see, so use a channel everyone can view.
Next step: we check how long the link lasts. - Check and change the settings.
1. Under the link, a line says when it expires, with an Edit invite link button. Choose Edit invite link. A window titled Server invite link settings opens with four settings: Expire After, Max Number of Uses, Roles (Optional) and Grant temporary membership. Its buttons are Cancel and Generate a New Link.
2. How long it lasts. Discord's help page says a new invite shows 7 days by default, or whatever you last used for that channel. On our real-screen check the line said Your invite link expires in 30 days, so go by your own screen. The Expire After list on a real screen offers: 30 minutes, 1 hour, 6 hours, 12 hours, 1 day, 7 days, 30 days and Never. Discord's help says a link that never expires needs a Community server, yet Never was listed on a standard server, so see the More box below. Example: you are inviting friends for a Saturday game night, so 7 days is plenty.
3. Max Number of Uses. The list offers No limit, 1, 5, 10, 25, 50 and 100. Example: you are inviting about 10 friends, so pick 10 (the list has no other numbers, so choose the next size up if yours is between two) and the link should stop working after the tenth person. Choose No limit for a link you will post publicly. No limit is what our real screen showed by default.
4. Roles (Optional). A dropdown that reads Select Roles. Opening it lists the roles your server has, each with a checkbox. A brand-new server has no roles of its own yet, so the list may be empty for you until you make some in the Roles & Permissions topic. We did not tick one or test it, so we cannot say for certain what it does. The wording of the temporary-membership note beside it suggests that people who join with this link get the roles you tick, but that is our reading, not something Discord's pages say. Leave it empty for now, and come back after the Roles topic if you want to try it.
5. Grant temporary membership. It is off by default. Leave it off for friends and community members. The screen says temporary members are automatically kicked when they disconnect unless a role has been assigned. Discord's help says that when it is on, people who join with the link are kicked when they disconnect unless you give them a role. It is meant for short visits.
6. Choose Generate a New Link, then copy the new link. Cancel leaves the old link as it was.
Next step: we send it. - Send the link. Paste it in a message to the people you want. Only share it where you are happy for anyone who finds it to join.
Next step: this topic is done. Design & Structure is the next topic.
More about invites: never-expiring links, removing one, custom links
- A link that never expires needs a Community server, per Discord's Invites 101 page. Discord's server types page agrees: it says Community server invite links never expire. The two pages disagree with what we saw: on a standard (not Community) server, the Expire After list still showed Never. We did not choose it, so we cannot say if the link then really never expires, or if it gets a time limit anyway. If you want to be sure a link stops working, pick a time instead of Never.
- Removing an invite. Open Server Settings, then Invites, and click the x next to the invite. There is also a Pause Invites option. Discord says a deleted invite's code cannot be made again, and that Discord support cannot recreate it either.
- A custom link (a short, readable address in place of random letters) needs the server to reach Level 3 Server Boost. Server Boost is a paid feature where members pay to unlock perks. We read this on a summary of Discord's page, not the full page. The setting is under Server Settings, then Boost Perks, in the Custom Invite Link section. A new server cannot do this yet.
More: if something does not look like this guide
I cannot find Add a Server
Discord says it can be hidden if you are in a lot of servers. Scroll down the server list on the left. If you are on a phone and the screen looks different, go by the words on your screen. Discord's guides do not cover the phone app.
My picture was refused or looks wrong
Discord's minimum is 128 by 128 pixels. Try a larger, square picture. If you crop a big one, crop it in multiples of 128.
I do not see Enable Community
Open Server Settings of the server you created, and scroll down the left sidebar. Discord's page does not say who can see it. If it is still missing, tell us exactly what the sidebar shows.
I turned on Community and now I am stuck with settings I did not expect
Turn it off: Server Settings, Community Overview, then the red Disable Community button at the bottom. Discord's page does not say whether the verification level and media filter go back to what they were, so look at them yourself afterward. We have not tested this.
Before you start
This topic is about the layout of your Discord server: which channels exist and how they are grouped. A channel is one room in the server. A text channel (shown with a # sign) is for typing. A voice channel (shown with a speaker icon) is for talking. A category is a labeled group of channels, like a folder.
What you need: a server you created (see the Create Your Server topic), and to be the server owner, or to have a role with the Manage Channels permission. Discord's page says that permission lets a role create and delete text and voice channels. A permission is a switch that lets a role do something. A role is a label you give to members.
These steps happen in Discord on your computer, in the desktop app or in a browser. Discord's pages also describe the phone app, but we have not checked the category steps there. If your screen differs from the words here, go by your screen.
First, we are going to plan the layout on paper, so you build it once instead of rearranging it later.
Plan your layout first
This step is not done in Discord. Use a notepad. First, we are going to write down your categories, then put channels under each one.
- Write your categories. Think of one category per purpose: where people read the basics, where they chat, where they talk. Discord's own example, a made-up eSports group, uses categories named Welcome, one per team, and Voice Channels.
Next step: we add the channels. - Put channels under each category. Here is a worked example for a made-up server called Maple Street Gamers. It is our suggestion for a small server. It is not a Discord rule, and you should use your own names.
• Category Welcome: #welcome, #rules, #announcements
• Category Chat: #general, #off-topic
• Category Voice: Lobby, Game Night
Discord's page recommends having a welcome channel, so new people can read about the server and so you can see when someone joins. It also says the announcements channel can be readable by everyone while only admins and moderators post in it. The Roles & Permissions topic covers that.
Next step: we build it in Discord.
Start small. Discord's Advanced Community Server Setup page ends by saying you can add and remove channels and settings as your server grows.
Start here. Your server exists and your plan is on paper.
Build it: categories, then channels
These steps happen in Discord, on your computer. First, we are going to create your first category.
- Create a category.
1. Click your server's name at the top of the channel list. The menu that opens has Create Channel and Create Category in it, just under Server Settings. (Discord's older page describes right-clicking the server's icon instead.)
2. Choose Create Category. A window titled Create Category opens with a Category Name box (the hint reads New Category) and a Private Category switch, which is off by default. The switch's line says that by making a category private, only select members and roles will be able to view it, and that linked channels in the category will automatically match this setting. The buttons are Cancel and Create Category.
3. Type the category name. Example: Welcome.
4. Leave the switch off unless you want a hidden category (the crimson section below covers that). Then press Create Category.
5. Repeat for your other categories. Example: Chat and Voice.
Next step: we create a text channel inside the first category. - Create a text channel.
1. Hover over the category where the channel should go. A plus sign (+) appears. Press it.
2. A window titled Create Channel opens. Under the title it says in and the name of that category, so you can confirm where the channel will land. (There is no extra menu first.) It has a Channel Type list. On a standard server we checked it offered three: Text (Send messages, images, GIFs, emoji, opinions, and puns), Voice (Hang out together with voice, video, and screen share) and Forum (Create a space for organized discussions). Text is already selected. We did not see Announcement in that list.
3. Type the channel name in the Channel Name box, which shows new-channel as a hint. Below it is a Private Channel switch (off by default) with the line: only selected members and roles will be able to view this channel. Leave it off for a channel everyone should see.
Example name: rules. Discord's examples are short lowercase words, like #general and #patch-notes.
4. Press Create Channel.
5. Repeat for each text channel in your plan.
Next step: we create a voice channel. - Create a voice channel. Discord's Voice Channels page gives two ways.
Way 1: press the plus (+) next to the category, choose Voice, type a name (example: Lobby), and press Create Channel.
Way 2: right-click the channel list, choose Voice, type a name and press Create Channel. Discord says this puts the channel at the very top, and you then drag it into a category.
Way 1 is easier, because the channel lands in the category you want.
Next step: we move things around if needed. - Drag to reorder. Discord says you can drag and drop channels and categories wherever you like in the channel list. If you drag a channel into a different category, Discord asks whether to sync permissions (we saw this on a real screen when dragging a voice channel into a private category). The window is titled Sync permissions? and asks Would you like to sync [channel] permissions with [category]? Its buttons are Cancel and a red Sync Permissions. There is no button that says "move without syncing", but Cancel does not stop the move: when we pressed it on a second channel, the channel still moved into the category, and its Permissions tab showed Permissions not synced with category with a Sync Now button. So a channel moved with Cancel keeps its own permissions and does not take the private category's. Press Sync Now to fix it. When we pressed Sync Permissions, the channel stayed in the private category and its Permissions tab no longer showed the not-synced banner. Read the crimson section below before you answer that.
Next step: renaming or deleting a channel. - Rename or delete a channel.
1. Open the channel's settings. Discord's pages say to hover over the channel name and press the cogwheel (gear), or on a phone to tap and hold the channel and choose Edit Channel.
2. A settings screen opens for that channel. Down its left side are Overview, Permissions, Invites and Integrations, then a red Delete Channel at the bottom. On Overview you will find a Channel Name box, which is where you rename it, and a Channel Topic box with a hint that says to let everyone know how to use the channel.
3. To delete, press Delete Channel. A window asks you to confirm and says This cannot be undone. Choose Cancel to back out, or the red Delete Channel button to go ahead.
We have seen these screens but have not renamed anything or saved changes, so check for a save button after you edit the name. We have not seen the equivalent screens for a category.
Next step: your layout is built. Check the Roles & Permissions topic next, so the right people see the right channels.
Channel types
Most servers only need text and voice channels. Here is what else Discord's pages describe. First, we are going to look at each type, so you can tell which you need.
Text, voice, forum and announcement channels, and what each needs
- Text channel. A # channel for typing, sharing files and ongoing chat. To chat in one, a member needs three permissions on: View Channel, Send Messages and Read Message History, Discord says.
- Voice channel. For voice and video. Discord's page says a lock icon on one means you do not have permission to join it. Voice channels also have their own text chat: press the Open Chat bubble to the right of the channel's name.
- Forum channel. A channel where each topic is its own post, so conversations do not talk over each other. Discord's help says it needs Community turned on (see the Create Your Server topic). Yet Forum was listed in the Create Channel window on a standard server we checked, so it may not be blocked. We did not create one. Create it the same way as a text channel, but pick Forum. Discord says forums are more lasting than threads (a thread is a side conversation started from one message, which is more temporary).
- Announcement channel. A special text channel with a Follow button, so other servers can receive your updates. It also needs Community. Create it with the plus sign and pick Announcement. To turn an existing channel into one, hover its name, press the Edit Channel icon, toggle on Announcement Channel, and press Save Changes. After you post, a Publish button appears. Press it to send the message to following servers. Discord says there is a limit of 10 publishes per hour, and that @everyone and @here mentions do not reach following servers. Discord says to give posting permission only to trusted members.
- Stage channels also exist, but they need Community and we have not covered them.
Next step: we look at private categories and moving things.
This section changes who can see what. Read it before you drag or hide anything.
Private categories, and moving things later
Permissions on a category can pass down to the channels inside it. That is handy, and it is also how a channel can end up visible to the wrong people. First, we are going to look at how a category's permissions reach its channels.
- Understand synced and not-synced. Discord's category page says a channel is either synced (its permissions completely match the category's) or not-synced. If you change the category's permissions, every synced channel updates automatically, and not-synced channels do not. Both kinds can live in the same category.
Next step: we see how a channel becomes not-synced. - Know what moves it out of sync. If you drag a channel into another category and press Cancel when asked to sync, or you change one permission on the channel itself, it becomes not-synced. To bring it back in line, open that channel's permissions and press Sync Now, Discord says. We saw this on a real screen: on a channel we had just made private, the Permissions tab showed Permissions not synced with category: Text Channels with a Sync Now button. So switching on Private Channel on one channel takes it out of sync with its category. That tab also had a Private Channel switch, a Who can access this channel? section with an Add members or roles button, a Roles list (ours said No Roles), a Members list (only the server owner, with an x to remove) and an Advanced permissions section lower down. Pressing Sync Now would make the channel match its category again; we did not press it.
Next step: we hide a category from everyone except one group. - Make a category private (only if you want one). Discord's example does this for a team's channels. Their steps, from a page marked "3 years ago":
1. Easiest, when you first create the category: turn on the Private Category switch in the Create Category window (we saw that switch on a real screen). For a category that already exists, Discord's page says to right-click the category name and choose Edit Category, where the same Private Category switch should be (we have not seen that screen).
2. With Private Category on, Discord says this makes the category sync its permissions to all text and voice channels under it.
3. On a real screen, pressing Create Category with the switch on opened a second window titled Add members or roles, with the category's name under the title. It has a box with the hint e.g. Moderators, @wumpus and the line Add individual members by starting with @, or type a role name. Below is a Roles list with a checkbox for each role your server has (ours showed one role, viewer). The buttons are Back and Skip. Tick the roles that should see the category, or press Skip to decide later. We pressed neither, so we have not tested what happens if you skip.
3. In its permissions, select @everyone (every member) and turn View Channel off. Discord says this is the main setting that hides the channels.
4. Add the role that should see the channels (example: a role called Team Apple) and turn View Channel on for it.
Roles and permissions are explained properly in the Roles & Permissions topic. We have not tested these steps on today's screen.
Next step: if people say they cannot see a channel, check the troubleshooting list below.
An older permission name you may see, and unread-message settings
- Older name. The six-year-old category page says that turning off a permission it calls Read Text Channels & See Voice Channels makes channels invisible to members who lack access, instead of showing them with a lock. Newer pages call the matching switch View Channel. We expect they are the same setting, but no page says so. Go by your screen.
- Muting and collapsing. Discord says that if you mute a category you still see which channels have unread messages but get no notifications; if you collapse it, only channels with unread messages show and you still get notifications; if you do both, the channels are hidden until you are mentioned directly or a role you have is mentioned. This is each member's own setting.
- Deleting or renaming. The Discord pages we read do not cover deleting or renaming a channel or category, so we have not written steps for them.
Keep it lean, and the limits
Fewer channels are easier for newcomers. A server with a dozen empty rooms feels dead. Start with the layout you planned, and add a channel when people ask for one. This is our advice, not a Discord rule.
First, we are going to look at the numbers Discord says it enforces.
Discord's limits for channels and categories
From Discord's caps page (marked "7 months ago"):
- 500 channels per server. This count includes text channels, voice channels and categories.
- 50 channels in one category.
- 50 categories per server.
- 250 roles per server.
Example: if you use 3 categories, 6 text channels and 2 voice channels, that is 11 of your 500.
Next step: this topic is done. Roles & Permissions is the next topic.
More: if something does not look like this guide
I cannot create channels or categories
Discord says you need to be the server owner, or have a role with the Manage Channels permission, to create and delete text and voice channels. Check Server Settings, then Roles, then the role, then its Permissions tab.
I do not see Forum or Announcement in the channel type list
Discord says both need Community turned on. See the Create Your Server topic.
A member says they cannot see or use a channel
To chat in a text channel a member needs View Channel, Send Messages and Read Message History. Check the channel's permissions, and check whether the channel is synced to a category that is hiding it from them. A lock icon on a voice channel means that person cannot join it.
I moved a channel and its permissions changed
Moving a channel to another category can sync it to that category's permissions. Open the channel's permissions to see whether it is synced, and change the category's or the channel's settings as you intended. Pressing Sync Now makes the channel match its category again.
Discord says I have reached a limit
The limits are in the section above: 500 channels in total, 50 in one category, 50 categories. We found no Discord page that lists the exact error words.
Before you start
A role is a label you give to members. A permission is a switch that lets a role do something, like send messages or kick people. Instead of setting switches person by person, you set them on a role and then give the role to people.
What you need: a server, and to be its owner or have the Manage Roles permission. Discord says that as the creator of your server you do not need to give yourself any roles or permissions, because you always have access to everything.
These steps happen in Discord, on your computer. First, we are going to look at how roles stack, so the steps after make sense.
How roles work
Read this once. It answers most "why can this person do that?" questions. First, we are going to look at the three ideas that matter: @everyone, stacking, and order.
- @everyone is the starting point. Discord says a new server has one role, @everyone, and that it sets the permissions everyone has, even people with no other role. It is also the template for new roles.
Next step: stacking. - Roles stack up. Discord says a person's server-wide permissions are every "allow" from all their roles, added together, plus the allows from @everyone. Example: if the role Moderator allows deleting messages and the role Game Night allows nothing special, someone with both can delete messages.
Next step: order. - Order matters for who can change whom, and for color. Discord says roles run top to bottom. A person can only affect members whose highest role is below their own. The color you see for someone comes from their highest role. A new role starts just above @everyone, and you can drag roles up or down in the list.
Next step: we plan your roles.
Plan your roles
This is not done in Discord. Use a notepad. First, we are going to write down the roles you need and what each is for.
- List the jobs people do. Here is a worked example for the made-up server Maple Street Gamers. It is our suggestion, not a Discord rule, so use your own names.
• Moderator: a few trusted people who can delete messages and keep order.
• Game Night: a "who you are" role for people who play on game nights. Nothing special to do, but it can unlock a channel.
Discord's own example uses an administrator role, a moderator role, one role per team and a general member role. You do not need a Member role, because @everyone already covers everyone.
Next step: we build them.
A simple rule of thumb from us: keep "what you can do" roles (like Moderator) separate from "who you are" roles (like Game Night), so you can change one without the other.
Start here. Your plan is on paper.
Create a role, set its permissions, give it to someone
These steps happen in Discord, on your computer. First, we are going to open the roles screen and create your first role.
- Create the role.
1. Click your server's name in the upper left corner and choose Server Settings.
2. Open the Roles tab, under the People heading. The screen says Use roles to group your server members and assign permissions. At the top is a Default Permissions card for @everyone, which applies to all server members. Below it are a Search Roles box and a Create Role button, then your list of roles with a Members column and a small pencil (edit) button on each role. Press Create Role.
The screen also says that members use the color of the highest role they have on this list, and that you can drag roles to reorder them. It links to Need help with permissions?
3. Discord makes a role named new role the moment you press Create Role, and opens it in an editor titled Edit Role. So press it only once. Pressing it again makes a second new role, and you would have to delete the extra one. The editor has three tabs: Display, Permissions and Links. A Back button and a plus sign sit above your list of roles.
4. On the Display tab, replace the text in the Role name box. Example: Moderator. You can change it later. Below it is a Role Style section. Discord's help says you can pick a color from presets or use the Custom Color picker. Example: green for Moderator, so people can spot them in chat. We did not see the rest of that screen.
5. Look for a Save Changes button or bar and press it if one shows. We have not seen where it sits, and the role already exists before you press anything, so check your list of roles afterward to see that the name stuck.
Next step: we set what the role can do. - Set its permissions.
1. With the role selected, open its Permissions tab. It has a Search permissions box, a Clear permissions link, and a heading General Server Permissions with on/off switches beneath it, the first being View Channels.
2. Turn on only what the role needs. Example: for Moderator, think about deleting other people's messages, and nothing more. We have not read a Discord page that explains each server-wide switch, so read the label and Discord's short description on screen before you turn one on.
3. Leave Administrator off. The crimson section below explains why.
4. Press Save Changes.
Next step: we give the role to a person. - Give the role to a person. Discord's page gives two ways:
Way 1: open the Members tab (under People in Server Settings; Discord's older page calls it Manage Members). On a real screen that page is headed Server Members and has a Show Members In Channel List switch near the top. We could not see the member list on a small phone window, so use Discord's steps here and go by your screen, pick the person, and choose the role.
Way 2: press the person's avatar (their picture) in the server, then press the plus sign under the role section and choose the role from the pop-up.
Discord's page for this is four years old, and another older page says to make sure @everyone is selected at the top right if names are missing. Go by your screen.
Next step: we put the role in the right order. - Put the role in order. In Server Settings, Roles, drag the role up or down in the list. Roles higher up can affect roles below them. Example: keep Moderator above Game Night, and keep any role you do not want moderators to change below Moderator.
Next step: we set channel permissions.
Channel permissions: make one channel different
Server-wide permissions are the default. A channel can add its own rules on top. Discord says channel permissions override server permissions. These steps happen in Discord, on your computer. First, we are going to open one channel's permissions.
- Open the channel's permissions.
1. Hover over the channel and click the cogwheel (cog icon) next to its name. This opens the channel settings.
2. Open the Permissions tab.
3. Discord says @everyone starts with access to all features of a channel. You can allow or deny what everyone can do here.
Next step: we learn the three marks. - Learn the three marks. For each permission you will see one of three marks, Discord says:
• a checkmark: on (allowed)
• an X: off (denied)
• a slash (/): not set here, so the default applies
Next step: we add a role. - Add a role and set its marks.
1. Press the plus sign to add a role or a person.
2. Select the role, then set each permission with the checkmark, X or slash.
3. Press Save Changes.
Worked example, for a channel called #announcements where everyone should read but only moderators should post: select @everyone and turn Send Messages to X. Then add the Moderator role and turn Send Messages to a checkmark. Leave View Channel on for everyone. Discord's own example sets up an announcements channel the same way.
Next step: if you want a channel only some people can see, we make it private. - Make a channel private (only if you want one).
1. Right-click the channel and choose Edit Channel, then Permissions. (On a real screen the channel's settings list shows Overview, Permissions, Invites and Integrations, with a red Delete Channel below; open Permissions.)
2. Turn on Private Channel. Discord says this removes View Channel from @everyone automatically.
3. You will see a list of roles with access. Press Add members or roles to let more in.
People who cannot see a text channel do not see it in their channel list, one older Discord page says. Discord's page on categories covers doing the same for a whole category.
Next step: we look at what each permission does.
What each channel permission does (from Discord's page)
- View Channel. Lets members see the channel. If off, they cannot view it.
- Manage Permissions. Lets members change this channel's permissions.
- Manage Webhooks. Lets members create, edit or delete webhooks in this channel (see the Webhooks topic).
- Create Invite. Lets members make invite links for this channel.
- Send Messages. Lets members post.
- Send Messages in Threads, Create Public Threads, Create Private Threads, Manage Threads. Threads are side conversations started from a message. Manage Threads lets members rename, delete, close and slow-mode them.
- Embed Links and Attach Files. Show previews of links, and upload files or media.
- Add Reactions. If off, members can still use reactions already on a message.
- Use External Emoji and Use External Stickers. Use emoji and stickers from other servers, if the member has Discord Nitro (Discord's paid plan).
- Mention @everyone, @here, and All Roles. Lets members ping everyone or any role.
- Manage Messages. Lets members manage other members' messages.
- Read Message History. Lets members see earlier messages.
- Send Text-to-Speech Messages and Use Application Commands (commands from apps and bots).
To chat in a channel, a member needs at least View Channel, Send Messages and Read Message History.
The exact order Discord applies permissions, with an example
For a channel, Discord says it starts from the person's server-wide permissions, then applies these in order:
- 1. denies for @everyone on the channel
- 2. allows for @everyone on the channel
- 3. all of the person's role denies, added up and applied at once
- 4. all of the person's role allows, added up and applied at once
- 5. denies for that specific person, if any
- 6. allows for that specific person, if any
Worked reading of that order (our reading, not tested): in #announcements, @everyone has Send Messages set to X (step 1). The Moderator role has it set to a checkmark (step 4, which comes after). So a moderator can post and an ordinary member cannot. A setting for one specific person (steps 5 and 6) comes last and wins over roles.
Next step: we look at the two settings that can cause real damage.
Read this before you give anyone more power.
Administrator, and who can change whom
Some switches are much more powerful than they look. First, we are going to look at Administrator, then at the limits on who can change whom.
- Administrator. Discord says this is the most powerful permission: it grants every permission and ignores all channel restrictions. It says to assign it with extreme caution. To see it, open Server Settings, Roles, pick a role, open Permissions, and look under Advanced Permissions for the Administrator toggle. Our advice: do not turn it on for anyone but yourself. You are the owner and do not need it. Give a trusted helper specific permissions instead.
Next step: Manage Roles. - Manage Roles. Discord says someone with this can create and change roles below their own, but can only hand out permissions they have themselves. Example: if their role cannot ban people, they cannot give a role the ban permission. They cannot change roles at or above their own. It is under General Server Permissions on the Permissions tab.
Next step: the ban and kick limit. - Equal or higher roles are protected. Discord says members cannot ban, kick or change nicknames of people with an equal or higher role, even if they have those permissions. This is why role order matters. Put your moderators below you and above ordinary roles.
Next step: check what a role really sees.
Check your work: View Server As Role
Instead of guessing what members can see, Discord lets you look at your server as a role would. Discord says this is for the owner and people with Administrator. First, we are going to turn it on for one role.
- Turn it on.
1. Open Server Settings, then Roles, and pick a role.
2. Scroll to View Server As Role in the Display tab. Discord says you can also use the three dots (ellipsis) next to a role's name.
3. A control bar appears at the top of Discord. Look through your channels. You see only what that role can see. We tried it on a test server: a role with no permissions could not see a text channel we had made private, but it still saw a voice channel we had left alone. So Private Channel hides a channel from a role that was not added to it.
Next step: try several roles, then turn it off. - Try several roles, then exit. Press Select Roles in the bar to view as several roles at once. When you are done, press Disable in the bar. Back to Roles Settings takes you back to the role. Discord notes it does not show voice limits like suppression or priority speaker.
Next step: this topic is done. Webhooks is the next topic.
More: if permissions are not doing what you expect
Someone has permissions I did not mean to give them
Common causes, from how Discord says permissions combine: they have another role whose allows add up; @everyone allows it; or a channel setting for them or their role allows it. Use View Server As Role to check, and look at the channel's Permissions tab for a specific person's settings, which win last.
A member cannot see or use a channel
They need View Channel, Send Messages and Read Message History. Check the channel's permissions, and check whether the channel is synced to a category that hides it. See the Design & Structure topic.
I cannot change a role or kick someone
Discord says you can only change roles below your own, and cannot ban, kick or change nicknames of people with an equal or higher role. Check the order in Server Settings, Roles.
I locked myself, or a helper, out of managing the server
The only thing Discord's pages we read say is that the creator of a server always has access to everything, so the owner does not need roles to manage the server. We found no Discord page on recovering a helper's access. If a helper lost access, the owner can fix their role in Server Settings, Roles. We have not tested this.
What a webhook is
A webhook is a one-way mail slot into one channel of your Discord server. Discord gives you a long web address (a URL). Any program or website that sends a message to that address makes the message appear in the channel. No bot is needed, Discord's docs say.
What it can and cannot do. A webhook can only send messages to its one channel. It cannot read messages or reply to people. If you need that, you need a bot (see the Bots & Developer Tools topic). Discord's safety page says bots and webhooks often work together.
What you need: the Manage Webhooks permission, or to be the server owner. Discord says that permission lets someone create, edit or delete webhooks in a channel. You also need something to send the messages: a website that supports webhooks, a no-code service, or your own program. The Connect section covers those.
Some of Discord's webhook pages are old (2020 to 2022), so the words on your screen may differ. These steps happen in Discord on your computer. First, we are going to plan which channel and name to use.
Plan your webhook
This is not done in Discord. Use a notepad. First, we are going to decide where messages should land and what to call the webhook.
- Pick the channel. A webhook posts to exactly one channel. Example: a text channel called #updates. If you want messages in two channels, you make two webhooks.
Next step: the name. - Pick a name. Discord's safety page recommends at least a name, so you can tell webhooks apart. Example: Maple Updates. Discord's developer docs say a name can be 1 to 80 characters and cannot contain the words clyde or discord. Your screen may apply its own rule.
Next step: we create it.
Start here. You know the channel and the name.
Create a webhook
These steps happen in Discord, on your computer. First, we are going to open the integrations screen and create the webhook.
- Open Integrations.
1. Click your server's name in the upper left corner and choose Server Settings.
2. Open the Integrations tab, under the Apps heading. On a real screen it says to manage webhooks, followed channels and apps, as well as Twitch and YouTube settings for creators. Its first card is Webhooks, which shows how many you have (ours said 2 webhooks) and has an arrow to open it. Open that card to reach the same Webhooks screen described below.
Next step: we create it. - Create the webhook.
1. Find the button. Discord's five-year-old page calls it Create Webhook, but on a real screen it is named New Webhook. We saw it in a channel's own settings: open the channel's settings, choose Integrations, open the Webhooks card, and New Webhook is the blue button at the top of that screen. That screen is headed Integrations > Webhooks and has a list headed Posting to and the channel's name. Each existing webhook shows its picture, its name, and Created on a date by the person who made it, with an arrow to open it. We expect the same button under Server Settings, Integrations, but we have not seen that screen.
2. Pressing New Webhook makes a webhook right away. Press it only once, or you will have an extra one to delete. The new webhook appears in the list with a default name (ours was Spidey Bot, so do not be surprised by whatever name you get) and the plain Discord logo as its picture, with Created on today's date. Open its row (it expands in place). You see a picture with a small add-image button on it and a Remove link under it (that is the avatar, the picture that shows beside its messages; under it the screen says Minimum Size: 128x128), a Name box, and a Channel dropdown that picks which channel it posts to. Below those are two buttons: Copy Webhook URL and a red Delete Webhook. Example: channel #updates, name Maple Updates. Change the Name from the default to yours. There is no Save button on this panel. We changed the name, closed the panel and opened it again, and the new name had stuck, so changes save by themselves. We tested the name only, not the picture or the channel.
3. Press Copy Webhook URL. Only press this when you are ready to paste the URL straight into the service that needs it.
A channel's own settings also have an Integrations tab (its list reads Overview, Permissions, Invites, Integrations). Opening it shows a heading Integrations that says to manage webhooks and followed channels that post into this channel, and two cards: Webhooks (it showed 1 webhook, with an arrow to open it) and Channels Followed (it showed 0 channels, with a Learn More button). So this is a second place to find and manage the webhooks that post to one channel. We have not opened the Webhooks card, so we do not know if you can create one from there.
Next step: before you paste that URL anywhere, read the crimson section.
Read this before you paste the URL anywhere.
Treat the webhook URL like a password
Discord's developer docs describe a webhook's address as ending in two parts: the webhook's ID and a secret token. Discord's safety page says there is no check that a message sent to a webhook comes from a trusted source. So anyone who has your URL can post into your channel. First, we are going to look at how to keep it private.
- Keep it out of public places. Do not post it in a chat, a screenshot, a public repository or a forum. Only paste it into the service or program that needs it.
Next step: what to do if it leaks. - If it leaks, delete it and make a new one.
1. Open Server Settings, then Integrations, and find the webhook. Discord says the page lets you delete webhooks.
2. Press the red Delete Webhook button in that webhook's row. Discord's docs say deleting is permanent. A test delete asked for a confirmation first. We did not read its exact words, but it was an ordinary confirm-or-cancel question. Be sure you are on the right webhook's row before you confirm.
3. Create a new webhook with the steps above and put the new URL into your service.
Discord's safety page calls a leaked URL a non-permanent problem, such as spam, and says the URL is easy to change. It does not give steps for changing a URL, so deleting and recreating is our way, based on the deletion Discord does describe. We have not tested it.
Next step: connect your webhook to something.
Connect it to something
A webhook does nothing alone. Something has to send to it. Discord's pages describe these ways. First, we are going to look at them, so you can pick one.
- A service that supports webhooks. Discord's Intro page uses GitHub as its example. Steps from that page:
1. In your GitHub repository, open Settings, then Webhooks, then press Add webhook.
2. In Payload URL, paste your Discord webhook URL and add /github at the very end. Example, with made-up pieces: (your URL)/github. Discord stresses this: without it the messages do not display properly.
3. Set the content type to application/json.
4. Choose which events to send, then press the last Add webhook button.
Discord's developer docs list the GitHub events it supports, including push, pull_request, issues, release and fork.
Next step: other ways. - A service built for Slack. Discord's docs say you can add /slack to the end of the URL for services that send in Slack's format. They say a few Slack options are not supported (channel, icon_emoji, mrkdwn, mrkdwn_in).
Next step: no-code tools. - A no-code service. Discord's safety page names IFTTT and Zapier as services that connect many platforms to a webhook through a web form, and Discohook for one-off, nicely formatted messages. Discord says it does not endorse them. Some limit how many events one webhook can take, so you may need more than one webhook.
Next step: your own program. - Your own program. Discord's docs say you send an HTTP POST (a web request that carries data) to the webhook URL. The message must contain at least one of: text (up to 2000 characters), embeds, a file, or a poll. An embed is a styled message box with a title, color and fields. We ran the test below on a throwaway webhook and it worked:
On Windows, open PowerShell. This command takes the URL from your clipboard, so you never type or paste it into the command. Paste the command into PowerShell and press Enter. It stops and asks you to click Copy Webhook URL in Discord. Do that, come back to PowerShell and press Enter again. Do not copy the command again after copying the URL, because that replaces the URL on your clipboard. Never paste the URL into a chat.Read-Host "Now click Copy Webhook URL in Discord, then come back here and press Enter"; $u = Get-Clipboard; Invoke-RestMethod -Uri $u -Method Post -ContentType "application/json" -Body '{"content":"Hello from my webhook"}'
If it works, Hello from my webhook appears in the channel the webhook is set to, under the webhook's name. PowerShell printed nothing for us, which is normal: Discord's docs say a successful send can return no content. In our test the message landed in general, because that was the channel the webhook was set to, so check the webhook's Channel setting if it is not where you looked. If you get an "Invalid URI" error, the clipboard did not hold the URL. Click Copy Webhook URL again and retry.
Next step: the limits.
Webhooks are not bots, and what a webhook cannot do
- Webhooks only send. Discord's safety page says they cannot view messages. Bots can both view and send.
- No hosting needed. A webhook is just an address. A bot is a program that has to stay online somewhere.
- No login. Webhooks have no check on who is sending. Bots are authenticated with a token, and Discord says a stolen bot token can do serious damage.
- Forum and media channels. Discord's docs say a message to a forum or media channel must say which thread to use (a thread ID) or give a thread name to create.
- Webhook events are a different thing. Discord's developer docs also use "webhook" for messages Discord sends to a program you run, when something happens in your app. That is for developers and is not covered here.
Managing webhooks, and limits
First, we are going to look at where your webhooks live and the numbers Discord gives.
Edit or delete a webhook, and Discord's limits
- Manage them. On Server Settings, Integrations, Discord says you can see every webhook, who added it, when, and which channel it posts to. You can change its name, avatar or channel, copy its URL, or delete it.
- Integration cap. A server can have at most 50 integrations (bots, webhooks and other apps together), per Discord's Integrations page.
- Messages. Up to 2000 characters of text, and up to 10 embeds per message. Discord's 2022 safety page also lists embed limits: title 256 characters, description 2048, up to 25 fields, and 6000 characters in total.
- Speed. Discord's 2022 safety page says 30 messages per minute. Discord's developer docs say limits can change and should not be hard-coded. If you send too fast you get a "429" reply with a wait time, and you should wait that long.
- Webhooks per server. The 2022 safety page says 10 per server. The newer Integrations page gives a 50-integration cap and does not mention 10. We do not know which holds today, so check on your screen.
Next step: this topic is done. Bots & Developer Tools is the next topic.
More: if your webhook messages are not showing up
Nothing appears in the channel
Check these, in order. Is the webhook posting to the channel you are watching? Open Server Settings, Integrations and look at its channel. Is the webhook still there? If it was deleted, Discord's docs say a deleted webhook returns a "404", and that a sender must stop using it, because repeated tries get a temporary restriction. Is the sender using the full, correct URL? Is it sending at least some text, an embed, a file or a poll?
GitHub messages look wrong, or do not arrive
Discord's Intro page says the URL must end in /github and the content type must be application/json. Check both in GitHub's webhook settings.
It worked, then stopped when I sent a lot
You may be sending too fast. Discord's docs say a rate limit gives a "429" reply with a wait time. Wait that long, then send slower.
I want the webhook to read or answer messages
A webhook cannot. Discord's pages say webhooks only send. You need a bot. See the Bots & Developer Tools topic.
My webhook URL leaked or someone is spamming my channel
Delete the webhook in Server Settings, Integrations, then create a new one and update your service. See the crimson section above. We have not tested this.
What an app and a bot are
On Discord, an app is a program that adds features to Discord. Discord's pages use "app" for what many people still call a bot. When an app is added to a server it can have a bot user, which shows up in your member list like another member and does its job there: welcome messages, music, moderation, games and so on.
Bot or webhook? A webhook can only send messages into one channel. An app with a bot user can also react to people, use slash commands (typing / to pick a command) and more. If you only need messages posted, the Webhooks topic is simpler.
What you need: to add an app to a server you need the permission to manage that server, or to be the owner. Discord's help says apps are added from the App Directory or an app's own invite link. Some of Discord's app pages are two years old, so the words on your screen may differ. These steps happen in Discord on your computer. First, we are going to pick an app and find it.
Start here. You have a server and an app in mind.
Add an app to your server
These steps happen in Discord, on your computer. Discord describes two ways to find an app. First, we are going to look through the App Directory.
- Find the app.
1. Discord's help says apps can be discovered through the App Launcher and the App Directory. Discord's App Directory page says you can open the directory three ways on a computer: right-click your server's icon, hover Server Settings and choose App Directory; or click your server's name, then Server Settings, then App Directory in the left list; or click your server's name and choose App Directory from the menu. The last two we saw on a real screen. On a real screen it appears in two places: in the menu that opens when you click your server's name, and in Server Settings under the Apps heading, next to Integrations. In Settings it carries a small arrow-out-of-a-box icon, which suggests it opens outside the settings screen (we have not clicked it).
2. Browse the collections, browse by category, or search by a term. Each app has its own product page, written by its developer. It can show the app's categories, links to the developer's website, popular slash commands, and sometimes an invite to a Discord server where you can try the app or get support. Example: a welcome-message app. Discord says the page's Copy Link button lets anyone share an app with their server admin, and that only admins add apps.
3. Discord's help says some apps carry tags such as In-App Purchases, Ad-Supported, Partner or Promoted. Read them before you add the app. We do not know what those tags guarantee beyond their names, so do not treat Partner or Promoted as proof an app is safe.
Next step: we add it. - Add it.
1. Choose Add App on the app's page.
2. A window opens. We saw it for the app Watch Together. It starts with This will allow the developer of [app name] to: and a list. Each line has a tick if the app asks for it or a grey x if it does not. Ours showed a tick next to Create commands and a grey x next to a joke line, Buy you a nice seafood dinner, so read the ticks, not just the words. Discord's help says apps can also ask for things like creating and editing channels, sending messages, connecting to voice and viewing the Audit Log.
3. Below the list is Add to server: with a dropdown that reads Select a server, and the line This requires you to have Manage Server permission in the server. There is also a note that the developer's privacy policy and terms of service apply to the app, with links, and a line such as Active since Aug 25, 2021. The buttons are Back and a purple button that reads You missed some fields until you pick a server. Pick your server in the dropdown, and the button changes to Authorize.
4. Press Authorize only if you are happy with the ticked list. If you are not, press Back. When it works, a window with a green tick says Success! and [app name] has been authorized and added to [your server]. It has two buttons: Close and Go to [your server].
Next step: check that it arrived. - Check that it is there. Open Server Settings and then Integrations. On a real screen that page is headed Integrations and says to manage webhooks, followed channels and apps, as well as Twitch and YouTube settings for creators. Scroll down to a section headed Bots and Apps. Each app there shows its name, Added on a date by the person who added it, a Bot tag if it has a bot user, and a Manage button with an arrow. If the app has a bot user, it should also appear in your member list.
Next step: before you rely on it, read the crimson section.
Apps with an invite link instead
- Some apps are not in the App Directory and give you an invite link on their own website. Opening that link in your browser takes you to a Discord screen where you pick a server and authorize, like the steps above.
- An invite link comes from the app's maker, not from Discord. We can only say what Discord's own pages say: read the permission list before you authorize, whatever the source.
Read this before you give an app more power.
Safety and permissions
An app can only do what its permissions allow. Discord's help gives you places to see and limit those permissions. First, we are going to look at what an added app is allowed to do.
- See what the app was granted. Discord says an app with a bot user gets a role of its own. The quickest look is the app's Manage screen: open Server Settings, Integrations, and press Manage next to the app under Bots and Apps. Scroll to the Bot section. It shows the app's name with an APP tag, its Role (a chip with the role's name), then two lists: Granted permissions, each with a green check, and Denied permissions, each with a red X. Read the granted list. The one to watch is Administrator: it should sit under Denied unless you meant to give it. A granted Manage Roles means the app can create and change roles below its own. Then do the next part, to edit the role itself.
1. Open Server Settings and then Roles. The app's role is in that list.
2. Find the role named after your app and open it. You can edit it like any other role (see the Roles & Permissions topic).
3. Turn off anything the app does not need. Example: a welcome app does not need to connect to voice.
Next step: the server-wide app permissions. - Check who can use apps. On Server Settings, Roles, Discord's help names a group of three permissions for apps (on a real screen they sit under a heading named Apps Permissions on a role's Permissions tab; to find them fast, type external apps in the Search permissions box. Use Application Commands and Use Activities also appear in an app's Granted permissions list on its Manage screen. On our server, Use External Apps was switched on for @everyone, and its one-line description begins Allows apps that members, but we could not read the rest): Use External Apps, Use Application Commands and Use Activities. Discord's page has a chart that relates the three. We do not repeat the chart, so read it on Discord's help page Moderating Apps on Discord if you want exact details.
Next step: limit one app's commands. - Limit one app's commands. Discord says Command Permissions are found under Server Settings, Integrations, by selecting the app. On a real screen, press Manage next to the app under Bots and Apps. The top of that screen has a Command Permissions section that says it restricts usage of this application's commands to roles, users and channels. It has two boxes: Roles & Members, with an Add Roles or Members button, and Channels, with an Add Channels button. By default each has one row, @everyone and All Channels, with a red X and a green check you can press; the check was selected. Below, the screen lists the app's commands, or says This application has no commands if it has none (ours had none). We have not changed any of these on a real screen. Discord's Command Permissions page adds: by default commands work in all channels, so when you add a new app every member can use any of its commands, unless the app's developer set default restrictions; you restrict them by turning a toggle off, or by pressing Add Roles or Members or Add Channels; clicking a single command opens a pop-up where you can change just that command; members without permission do not see the command when they type /; and command permissions can only be changed on a computer, though they apply on every device.
Next step: check what an app can see. - Know what it can see. Discord's help says an app's profile has a Data Access tab that shows what the app can see. Open the app's profile and look there.
Next step: one warning.
One warning from Discord. Discord says AutoMod does not flag apps that are installed in a server. So an app you add can post things AutoMod would catch from a person. Only add apps you trust.
Remove an app
First, we are going to remove an app you no longer want. Discord's help describes two different cases.
- An app in your server. Discord's What Are Apps page says to right-click the app's bot in the Members list and choose Kick, and that you need to be the owner or have Manage Server. But not every app has a bot in the member list: we added Watch Together to a test server, and it did not show up as a member at all, though it did appear under Bots and Apps. So the Members route can fail. Use the next route instead. We tested it: Remove App brought up a confirmation screen, and after we confirmed, the app was gone from Bots and Apps. On a real screen, the app's Manage screen (under Server Settings, Integrations, Bots and Apps) ends with a red Remove App button. Beside it the screen says that removing this integration removes any apps, including bots and webhooks, on this page from your server, and that this cannot be undone. We did not press it. The older way, which Discord's help page gives: kick the bot, like removing a member. Find the bot in your member list, open its menu (right-click it on a computer) and choose the kick option. Discord's Integrations page also lists the app, so check that it is gone from Server Settings, Integrations afterward. We have not run this on a real server.
Next step: apps on your own account. - An app on your account. Discord says apps added to your account, not a server, are removed with Deauthorize. Discord's What Are Apps page gives the path: User Settings, then Authorized Apps, then Deauthorize next to the app. We have not seen that screen.
Next step: this topic's last part, building your own.
Build your own app, the first look
This part is only for people who want to make their own bot. It needs programming, and we do not teach programming here. We cover the Discord side. Discord's own tutorial, Building your first Discord Bot, does the coding with JavaScript, and it is the place to continue. First, we are going to create the app.
- Create an app. Open Discord's developer portal. Discord's own tutorial links its Create App button to the address discord.com/developers/applications (we read that from the tutorial page, not from your browser's bar, which showed only the site name on a phone). The portal home is headed PORTAL and says Welcome with your Discord name. Under Jump back in it lists your apps, each with a Go to app button and the team it belongs to (ours said Personal Team), and an Apps button sits beside that heading. There is also a plus button at the top. We did not press it, so we cannot say it is the create button. Discord's tutorial says: press Create App, type a name, and press Create. Example: Maple Helper. You land on the General Information page, which shows an Application ID.
Next step: the token. - Understand the token. A new app has a bot user by default. On the Bot page you see a Username box, then Token, with this line: For security purposes, tokens can only be viewed once, when created. If you forgot or lost access to your token, please regenerate a new one. Under it is the button Reset Token, which makes a new token. Further down is an Authorization Flow section with a Public Bot switch. Its note says public apps can be installed by anyone, and when it is unchecked only you can install the app. Ours was off, which is the safe choice for a bot you made for your own server. Discord says the token authorizes requests and carries the app's permissions, so it is highly sensitive: never share it or put it in version control. It is shown once, so keep it in a password manager. Never type it in a chat, here included.
Next step: the install link. - Set up the install. On the Installation page, under Install Link, choose Discord Provided Link. Under Default Install Settings, for a server app add the bot scope and the applications.commands scope. When you pick bot, a Permissions menu appears. Pick only what the bot needs. Discord's example picks Send Messages.
Next step: install it on a test server. - Install it somewhere safe. Discord says to test in a server nobody else uses. Copy the install link, open it in your browser, choose Add to server, and pick your test server. The bot should then appear in the member list. The bot will be silent until your program is running, and Discord's tutorial covers that.
Words you will meet
- Scope. A permission slip the person installing the app approves. Discord names bot and applications.commands in its tutorial.
- Installation context. Where an app can be installed. Discord's options are User Install (on a person's account) and Guild Install (in a server; Discord's developers say "guild" for server).
- Intents. Settings on the Bot page. Discord's tutorial says some are "privileged" and may need to be turned on depending on what your app does. We did not read the page that explains them, so we do not say which ones you need.
- Public Key. A value on the General Information page that Discord's tutorial says is used to check that web requests come from Discord. It is not the token.
Next step: this topic is done. If something went wrong, the troubleshooting list below may help.
More: if something went wrong
I added the app but nothing happens
Check these. Is the app listed in Server Settings, Integrations? Does it have a role, and does that role have the permissions it needs, in both Roles and in the channel? Are the three app permissions in Roles turned on for the people using it? If it still does nothing, Discord's What Are Apps page says apps are created and run by their developers, so go to the app's support server or contact the developer. Discord says most support servers are listed in the app's Overview section in the App Directory. If you think an app breaks Discord's rules, Discord says you can report it.
Slash commands do not show up
Discord's help names Use Application Commands as an app permission and says command permissions are set under the app in Integrations. Check both, for the role of the person typing.
I do not know how to remove it
Use the Remove an app section above. Kicking from the member list only works if the app is listed there; some apps are not. For an app on your account, use Deauthorize.
My own bot is offline
Discord's tutorial says the app responds only when your program is running. We read nothing on why a bot would stay offline, so check that your program is running and read Discord's tutorial.
My bot token leaked
Discord's tutorial says the Reset Token button on the Bot page makes a new token. Our own reasoning, not a Discord page: that should make the old one stop working, so reset it, then put the new one only in your own program's private settings. Discord says the token carries your app's permissions. We read no page about steps after a leak, so also check what the bot did in your server.