Discord vocabulary is the language of servers, text channels, voice channels, roles, permissions, threads, forums, Nitro and AutoMod. Start with five words: server, channel, role, permission and invite link. A server is the community space, channels organise different kinds of conversation and roles determine what members can do.
The important distinction is role versus permission. A role is a named bundle or identity; permissions control actual actions. Discord explains that server permissions and channel-level overrides interact, and that role hierarchy determines some moderation capabilities. Giving someone the Administrator permission merely to let them post announcements creates unnecessary access risk.
Quick answer: Use a text channel for messages, a voice channel for live talk, a thread for a focused conversation and a forum channel for more persistent topic-based discussions. Read the server’s rules before posting, inspect permissions when a channel is missing and be suspicious of DMs demanding passwords or promising free Nitro.
- Joining: verify the server, invite link and rules.
- Finding conversations: distinguish text, voice, forum and thread.
- Understanding authority: inspect owner, administrator, moderator and roles.
- Participating: reply, mention, react and use voice controls appropriately.
- Community safety: understand AutoMod, timeouts, bans and reports.
- Protecting accounts: reject suspicious gift links and unknown bot permissions.
This is an independent practical Discord vocabulary guide for newcomers, hobby groups and community organisers. Explore eduKateSG Vocabulary Articles & Knowledge for other digital-language guides.
How a Discord server works in everyday language
Imagine a community that discusses video editing. It might have a welcome channel explaining rules, a general text channel for everyday questions, a forum for reusable tutorials and a voice channel for live workshops. An administrator could manage the server while ordinary members have limited permissions. This structure keeps conversations findable without demanding that everyone read every message.
Discord’s official server guidance says a server acts as a hub organised into text and voice channels. Its Forum Channels FAQ distinguishes persistent forum discussions from more temporary message threads. These differences help when deciding where to post a question that other people may need six months later.
Community Onboarding is another useful distinction. It can guide new members into relevant channels and roles based on questions, but it does not remove the need to understand permission settings or local rules. A missing channel might be a deliberate restriction rather than a technical failure.
Discord servers, channels and community structure
The following 33 terms form one part of Discord. Read the practical meaning and example; features differ by server configuration, account eligibility and device.
- Discord server — A digital space organised around a group, interest or community with its own channels and rules. Example: Join the hobby server through a valid invitation.
- Server owner — The account holding ultimate ownership of the server under Discord’s arrangements. Example: Ask the owner before making high-risk administration changes.
- Server administrator — A person with broad permissions to manage a server, often through the Administrator permission. Example: Give Administrator rights only when genuinely necessary.
- Moderator — A person helping manage members, messages and rules under the powers assigned to them. Example: Contact a moderator about a rule violation.
- Member — A person who has joined a server. Example: A member does not automatically have access to every channel.
- Community server — A server configured with community-focused tools and settings under Discord’s current eligibility rules. Example: Community servers can use Onboarding and other organisation features.
- Discoverable server — An eligible server made findable through supported discovery features. Example: Discoverability is not guaranteed for every community.
- Server list — The column or interface containing the servers the user has joined. Example: Look in the server list for the study group.
- Server icon — A graphic representing a server in the interface. Example: Recognise the server icon before clicking.
- Invite link — A URL used to invite eligible people to join a server under its settings. Example: Verify an unsolicited invite before joining.
- Invite expiration — A time or use limit after which a configured invitation may no longer work. Example: An expired invite requires a new link.
- Invite limit — A restriction on how many times a particular invitation can be used. Example: A one-use invite may stop working after admission.
- Text channel — A channel designed mainly for written messages, attachments or related discussion. Example: Post written questions in the help channel.
- Voice channel — A space for live voice participation under server permissions. Example: Enter the voice channel when ready to speak.
- Category — A grouping used to organise channels and often associated permissions. Example: Place help channels under a Support category.
- Channel topic — A short description of what belongs in a channel. Example: Read the topic before posting.
- Channel name — The label identifying a channel’s intended subject. Example: A clear channel name reduces misplaced questions.
- Announcement channel — An eligible community channel designed for publishing updates that may be followed elsewhere. Example: Keep official changes in the announcements channel.
- Forum channel — A channel type organising longer discussions into separate posts. Example: Create a forum post for a recurring question.
- Forum post — A topic-specific discussion within a forum channel. Example: Search the forum before opening another question.
- Thread — A focused conversation created from a message or related discussion, often more temporary than a forum post. Example: Use a thread to discuss one bug without flooding the main channel.
- Public thread — A thread accessible under the relevant channel and permission settings. Example: A public thread is not universally visible outside its server.
- Private thread — A supported thread restricted to invited members and people with appropriate permissions. Example: Private thread access is still governed by server roles.
- Pinned message — A message placed into a channel’s saved highlights under supported controls. Example: Pin the current server rules.
- Rules channel — A location describing acceptable conduct and community obligations. Example: Read the rules before participating.
- Welcome channel — A channel intended to orient new members. Example: Start with the welcome message.
- Onboarding — A Discord process that can guide new members through selecting relevant roles and channels. Example: Answer Onboarding questions to personalise the channel list.
- Default channels — Channels offered to new members through eligible Community Onboarding. Example: Provide a clear Help channel as a default.
- Channel list — The visible set of channels available to a member based on permissions and preferences. Example: A missing channel may reflect a role or view setting.
- Browse channels — A supported interface for discovering or choosing more channels within a server. Example: Browse channels to find specialised discussions.
- Server guide — A supported onboarding or community orientation feature showing useful resources and tasks. Example: Use the server guide instead of repeatedly asking where rules are posted.
- Event — A scheduled activity organised through server features or connected services. Example: Check the event time zone before joining.
- Stage channel — A voice-oriented channel type intended for structured presentations with speakers and an audience. Example: A stage session differs from an ordinary casual call.
Roles, permissions and moderation vocabulary
The following 35 terms form one part of Discord. Read the practical meaning and example; features differ by server configuration, account eligibility and device.
- Role — A named set of permissions or identity labels assigned to selected server members. Example: Assign a volunteer role without giving administrative powers.
- Role hierarchy — The ordering of roles affecting which roles or members can be managed through certain permissions. Example: A lower role usually cannot manage a role above its own position.
- @everyone — The default role applying to every server member, including people with additional roles. Example: Review @everyone permissions before opening a channel.
- Administrator permission — A powerful permission that grants broad server capabilities and bypasses many channel restrictions. Example: Never use Administrator simply to let someone post announcements.
- Manage Server — A permission allowing selected server configuration changes. Example: Manage Server should be limited to trusted staff.
- Manage Roles — A permission allowing management of eligible roles below the user’s highest role, under Discord rules. Example: Manage Roles is not the same as full ownership.
- Manage Channels — A permission governing changes to channels or channel configuration. Example: Grant Manage Channels only to organisers who need it.
- View Channel — A permission controlling whether a member can see a selected channel. Example: A channel may be hidden when View Channel is denied.
- Send Messages — A permission allowing a member to write in selected text channels. Example: A read-only announcements channel restricts Send Messages.
- Read Message History — A permission enabling members to see older messages in a channel under its rules. Example: Without history access a member may miss prior guidance.
- Connect — A voice permission controlling whether a member can join a voice channel. Example: Connect is different from permission to speak.
- Speak — A voice permission controlling microphone speech in supported voice channels. Example: A listening role may connect without speaking.
- Mute Members — A moderation permission for controlling certain members’ voice input. Example: Mute Members should not be granted casually.
- Move Members — A permission allowing movement of users between eligible voice channels. Example: Move Members affects live conversations.
- Kick Member — Remove someone from the server without necessarily banning them from returning. Example: A kick is not the same as a ban.
- Ban Member — Prevent a member from joining a server under the ban’s rules and conditions. Example: Ban should follow clear moderation criteria.
- Timeout — A moderation action temporarily restricting a person’s participation under applicable server rules. Example: Timeout is different from permanently removing an account.
- Role mention — A message that notifies eligible members associated with a role under allowed settings. Example: Avoid pinging everyone for routine updates.
- Channel permission — A role- or person-specific permission applied to one channel. Example: Channel permissions can change what a member may do there.
- Category permission — A permission configuration shared with or inherited by channels in a category under appropriate sync settings. Example: Check category permissions before altering a channel.
- Permission override — An Allow or Deny rule applied for a channel context that can modify server-wide permissions. Example: A channel override can restrict Send Messages for one role.
- Permission sync — Keeping a channel’s settings aligned with its category under supported controls. Example: An unsynced channel may behave differently from nearby channels.
- Private channel — A channel configured so only eligible members and roles can see it. Example: A private channel is not a substitute for strict confidential-data handling.
- Read-only channel — A channel where some members can view content without sending messages. Example: Use a read-only channel for verified announcements.
- Slowmode — A setting limiting how frequently a person may send messages in a channel. Example: Slowmode can reduce message flooding.
- AutoMod — Discord’s built-in moderation system applying selected keyword, spam and other rules to eligible content. Example: AutoMod can block certain risky messages before posting.
- Keyword filter — A rule detecting specified words or phrases for moderation under AutoMod. Example: A keyword filter can help block repeated spam links.
- Spam filter — A rule or system intended to detect disruptive repetitive messages. Example: Spam filters can misclassify legitimate content.
- Safety Setup — Server settings used to configure available moderation and protection features. Example: Review Safety Setup when managing a Community server.
- Raid — An influx of coordinated disruptive or abusive activity intended to overwhelm a server. Example: A raid calls for containment and careful moderation.
- Raid Protection — Discord tools intended to detect or mitigate suspicious join behaviour under eligible settings. Example: Raid Protection does not guarantee every attack is blocked.
- Verification level — Requirements that members must meet before performing selected activities under server policy. Example: Higher verification can create friction for genuine newcomers.
- Audit Log — A record of certain server administration or moderation actions visible to authorised staff. Example: Use Audit Log to investigate an unexpected role change.
- Report — A mechanism for notifying Discord or server staff of potential rule or policy violations. Example: Report a scam through appropriate channels.
- Appeal — A request to reconsider an enforcement decision under the server’s or platform’s process. Example: An appeal should explain the facts rather than harass moderators.
Messages, voice, calls and personal account tools
The following 35 terms form one part of Discord. Read the practical meaning and example; features differ by server configuration, account eligibility and device.
- Direct Message — A message exchanged outside a server channel with an eligible account, often called a DM. Example: An unexpected DM offering free Nitro may be fraudulent.
- Group DM — A conversation involving several accounts separate from a server’s channel structure. Example: A group DM is not a server.
- Username — An account identifier used for addressing or finding a member. Example: Read the username rather than trusting a copied avatar.
- Display name — A name shown in the interface that may not uniquely identify a person. Example: A display name is not proof of identity.
- Server nickname — A name used by a member inside one server under permission settings. Example: A server nickname can differ from the account display name.
- Mention — A reference to a user, role or group that may notify recipients under the relevant rules. Example: Use mentions only when a person needs the information.
- Ping — Informal term for notifying or mentioning someone. Example: Do not ping every member for a minor question.
- @here — A mention targeting some currently active members under permissions and notification settings. Example: Reserve @here for genuinely timely updates.
- @everyone mention — A mention capable of notifying the broader server membership under permissions and settings. Example: Avoid @everyone for routine chatter.
- Message reply — A response linked to an earlier message for context. Example: Reply to the question instead of starting an unrelated thread.
- Reaction — An emoji or other supported response attached to a message. Example: A reaction is not formal approval.
- Emoji — A graphical symbol used in text, reactions or server expression. Example: An emoji should not replace essential instructions.
- Custom emoji — A server-created or otherwise eligible emoji available under usage rules. Example: Custom emoji availability can depend on permissions.
- Sticker — A larger expressive graphic available through selected message tools. Example: A sticker can add tone without conveying factual confirmation.
- GIF — An animated image format often used in chat responses. Example: A GIF may make a channel harder to follow.
- Attachment — A file or image shared in a message under upload limits and settings. Example: Do not open a suspicious attachment automatically.
- Embedded link — A webpage preview or interactive item associated with a URL in chat. Example: A preview cannot prove the link is safe.
- Code block — A way of displaying monospaced code or structured text within a message. Example: Use a code block so software instructions preserve their punctuation.
- Spoiler tag — A formatting feature hiding selected content until the user chooses to reveal it. Example: Mark plot details as spoilers.
- Voice activity — A speaking mode that transmits sound when the microphone detects eligible activity. Example: Background noise may activate the mic.
- Push to Talk — A mode requiring a chosen key or control while transmitting voice. Example: Push to Talk can reduce accidental microphone transmission.
- Mute microphone — Turn off outgoing voice audio under the selected control. Example: Mute before leaving a meeting briefly.
- Deafen — Disable incoming audio, often also muting local voice under the client behaviour. Example: Deafen is not the same as leaving a channel.
- Screen Share — Transmit selected screen or application visuals in a supported call or voice channel. Example: Close private documents before screen sharing.
- Go Live — A Discord term or feature for streaming the screen or an application in eligible contexts. Example: Go Live is a stream, not a public television broadcast.
- Video call — A live conversation involving supported camera video. Example: Check camera permissions before starting.
- Voice channel connection — An active presence in a server’s live voice area. Example: Disconnect when the discussion is finished.
- Notification settings — Controls determining which messages or mentions create alerts. Example: Mute low-priority channels rather than ignoring important updates.
- Do Not Disturb — A presence or notification status designed to reduce interruptions. Example: Do Not Disturb is a preference, not a guarantee of unreachability.
- Invisible status — An online presence setting that can appear offline while allowing account use. Example: Invisible does not erase messages or account activity.
- Block user — A control restricting interactions with an account under the platform’s rules. Example: Block persistent harassment rather than arguing with it.
- Friend request — An invitation to form a direct Discord friendship or contact relationship. Example: Verify a friend request from an unfamiliar account.
- Message request — A pending or filtered contact attempt under privacy controls. Example: Review message requests cautiously.
- Nitro — Discord’s subscription product offering eligible personal enhancements under current plans and regions. Example: Nitro is not permission to bypass server rules.
- Server Boost — A paid contribution unlocking eligible improvements to a particular server under current rules. Example: A server boost does not grant ownership or moderator access.
Security, scams, privacy and healthy community language
The following 35 terms form one part of Discord. Read the practical meaning and example; features differ by server configuration, account eligibility and device.
- Community Guidelines — Discord-wide rules defining disallowed behaviour and content. Example: Server rules cannot authorise violations of Discord policy.
- Terms of Service — The contract governing use of Discord under current terms. Example: Read the service rules before building a commercial community.
- Server rules — Local community standards set by authorised moderators under platform policy. Example: Read server rules before advertising.
- Age-restricted content — Material subject to Discord’s age and access restrictions. Example: Check age restrictions before entering a channel.
- Sensitive content filter — An available control that helps handle certain content categories or media in DMs. Example: Filters cannot identify every harmful item.
- Privacy Settings — Account options controlling contacts, permissions and related exposure. Example: Review privacy settings after joining many servers.
- DM permissions — Rules influencing who may send a direct message under account and server contexts. Example: Limit unwanted DMs where supported.
- Friend request setting — A rule affecting which people may send friend invitations. Example: Restrict strangers’ requests if needed.
- Account verification — A process proving selected account attributes, different from verifying every statement made by a user. Example: A verified email does not prove a person is trustworthy.
- Two-factor authentication — A sign-in safeguard using an additional authentication method. Example: Protect recovery codes when enabling 2FA.
- Backup codes — Recovery credentials used if ordinary second-factor access is unavailable. Example: Store backup codes securely, not in a public channel.
- Passkey — A cryptographic credential available for some sign-in or account functions where supported. Example: Use passkeys only through official controls.
- Phishing — A deceptive message or link designed to steal account information or money. Example: An unsolicited login link offering Nitro can be phishing.
- Malicious bot — An automated account or integration intentionally used to harm, scam or spy. Example: Grant a bot only necessary permissions.
- Bot — A software-controlled Discord account providing automated features under its access rights. Example: Bots can post reminders or moderate content.
- Bot permission — A capability authorised for an integration in a server. Example: Administrator is usually excessive for a simple reminder bot.
- OAuth2 authorisation — A supported approval process granting an app specified account or server access. Example: Read the scope before accepting OAuth permissions.
- App integration — A connected service that provides features in Discord under its granted rights. Example: Review unused integrations periodically.
- Token theft — Unauthorised acquisition of access credentials enabling account or integration misuse. Example: Avoid downloading unknown executables from chat.
- Malware attachment — A harmful file shared through a message or download. Example: Scan suspicious attachments and do not execute them.
- Social engineering — Manipulation designed to make a person reveal secrets or take unsafe actions. Example: A stranger impersonating support is social engineering.
- Impersonation — Pretending to be a moderator, staff member, friend or organisation. Example: A copied staff nickname does not prove identity.
- Fake giveaway — A deceptive offer designed to steal access or financial information. Example: A giveaway demanding your password is suspicious.
- Nitro gift scam — A fraudulent message imitating a subscription gift or benefit. Example: Verify gifts through official Discord interfaces.
- Scam report — A report to the platform about suspected deceptive conduct. Example: Report a fraudulent bot or DM through official tools.
- Account recovery — A supported process for regaining access after lost credentials or compromise. Example: Use the official support route, not a stranger’s paid fixer.
- Server discovery — Finding communities through eligible directories, invitations or recommendations. Example: A discoverable server still requires judgement.
- Community moderation — The organised management of conduct, rules and enforcement. Example: Moderation requires fair criteria and documented decisions.
- Ban appeal — A request to reconsider a ban through an available process. Example: A polite appeal should not become harassment.
- Access review — A periodic assessment of roles and permissions for members and bots. Example: Review old moderator and integration rights.
- Consent — Meaningful agreement to share information or take an action. Example: Seek consent before recording or publishing private conversations.
- Personal data — Information that can identify or relate to an individual. Example: Do not post a home address in an open channel.
- Confidential channel — A channel intended for restricted discussion under specified permissions. Example: A private channel does not guarantee that screenshots cannot escape.
- Least privilege — Providing only the rights needed to perform a job. Example: Give helpers Send Messages instead of Administrator.
- Independent verification — Checking an important request through a separately trusted route. Example: Contact a known moderator before handing over login codes.
Five practical Discord problems and how the words help
1. You joined a server but cannot see the help channel
First distinguish visibility from a genuine app error. The server may use role-based View Channel permissions or ask new members to complete Onboarding. Some channels may be hidden until a role is assigned. Read the welcome information, inspect Channels & Roles if the server offers it, then ask a trusted moderator through the appropriate support channel. Do not demand Administrator just to see a resource.
2. A volunteer needs to post announcements
The principle is least privilege. The volunteer might need access to one announcements channel or permission to send messages there. They usually do not need Administrator, Manage Roles or unrestricted bot access. Check the server role, channel overrides and the position of their role in the hierarchy. Discord’s roles documentation specifically describes role hierarchy and channel permission controls.
3. A busy channel is filled with repeated questions
A thread can isolate a short conversation from the main channel, while a forum channel can preserve longer topic-specific posts under their own headings and tags. Choose the structure according to the life of the information. A one-hour technical issue may belong in a thread; a frequently used tutorial may deserve a forum post.
4. A stranger offers a free subscription in a DM
A message mentioning Nitro or showing an official-looking icon is not proof of a legitimate gift. Avoid sign-in links in unsolicited messages, never share verification codes and do not authorise bots or applications you do not understand. A genuine service does not need you to surrender a password to another user. Report the suspicious account through the product’s official tools.
5. A server is overwhelmed by spam
Moderators can combine appropriate rules, verification, Slowmode, AutoMod filters and Raid Protection where eligible. Discord describes AutoMod as a way to detect or block certain unwanted material before posting. However, automated filtering can produce mistakes, and higher verification can make it harder for legitimate people to join. Use clear enforcement criteria and review outcomes rather than assuming every flagged message is malicious.
Roles, channels and powers are different
- Role: a group of permissions and identity labels assigned to members.
- Server permission: a general capability such as managing roles or inviting people.
- Channel permission: a capability or restriction applied to a particular channel.
- Role hierarchy: an ordering that limits which roles or members can be managed in specified cases.
- @everyone: the default role applying to all server members.
- Administrator: broad access that should not be given for routine tasks.
- Moderator: a person assigned selected enforcement responsibilities.
- AutoMod: automated rule enforcement that supports but does not replace human judgement.
Mistakes that lead to confusion or security problems
- Server versus channel: a community can contain many channels.
- Thread versus forum: an attached conversation differs from a forum’s dedicated topic posts.
- Public server versus public channel: visibility within one server is not internet-wide visibility.
- Role name versus actual permission: being called “Moderator” does not establish what controls are enabled.
- Kick versus ban: removal without a ban differs from restriction on rejoining.
- Timeout versus ban: a temporary participation limit differs from server exclusion.
- Mute versus deafen: disabling your microphone differs from suppressing incoming audio.
- DM versus verified support: a private message from a stranger is not proof of official authority.
- Nitro versus Server Boost: personal subscription features differ from server enhancement contributions.
- Bot integration versus safe automation: a bot’s permissions can expose or alter important server content.
A sensible community safety routine
Before joining: check the invite’s origin, read server rules and avoid posting personal identifiers. A server’s popularity does not guarantee trustworthy moderators or content.
Before assigning roles: identify the exact work a member must do, then grant only the permissions needed. Review @everyone settings, category overrides and who can mention large groups.
Before installing a bot: examine the developer, requested access and purpose. Revoke old integrations and avoid granting Administrator for a simple reminder or poll.
Before sharing a screen: close confidential documents, turn off unrelated notifications and verify who can see the stream. Channel membership and privacy expectations matter.
After a concerning incident: use the server’s moderation process and Discord’s report function where appropriate. Document the factual issue without publishing private evidence to an open channel.
Practice your Discord vocabulary
- A community space with topic areas: server.
- A room for written messages: text channel.
- A longer discussion centred on a separate topic post: forum channel.
- A focused conversation stemming from a message: thread.
- Permission to see a restricted area: View Channel.
- An all-powerful permission that should be granted sparingly: Administrator.
- A temporary restriction on member participation: Timeout.
- Automatic keyword or spam rule enforcement: AutoMod.
- Group live listening or speaking without text: voice channel.
- A suspicious private offer that asks for account codes: possible phishing or impersonation.
Frequently asked questions
What is a Discord server?
A community space organised into channels with its own rules and permission configuration. Servers are not the same as a single group DM.
What is the difference between a channel and a thread?
A channel is a main organised space. A thread is a focused conversation attached to or generated from other discussion under the supported channel type.
Are Discord forum channels and threads the same?
No. Discord says a forum is a channel type and its posts are intended for more persistent, organised discussion; threads are a separate, often shorter-lived message structure.
Can someone with a Moderator role read every private channel?
Not necessarily. Their effective roles and channel permissions decide what they can access. A role name alone is not enough.
What does @everyone mean?
It names the default role associated with all members and may also be used as a broad notification mention under appropriate settings.
Is Discord Nitro required to join servers?
No. Many core server and messaging functions are free, while Nitro provides eligible subscription enhancements.
Are Discord bots safe by default?
No. Bots are integrations with permissions. Check what each can read, send or manage before authorising one.
What can I do about a fake Nitro giveaway?
Do not open unknown sign-in links or share codes. Verify through the official service, block the suspicious user and report the message where appropriate.
Official Discord documentation and related vocabulary
Server and account features can change as Discord updates its settings. These official guides explain the current concepts.