What you are actually controlling
Sharing a Discord username in a public profile, forum post or portfolio exposes you to two separate contact channels: friend requests and server direct messages. They are governed by different controls, and changing one does not necessarily change the other. Before you publish your handle, decide which channel strangers should be able to use, then set each control deliberately.
A username search is not a complete account inventory, and public matches are leads, not proof of ownership. The checklist below is about permissions on your own account, not about finding anyone else.
Step 1: Decide your contact policy before touching settings
Write down the answer to one question: should a stranger be able to reach you without a shared server? If the answer is no, you will restrict friend requests and review server DM permissions. If the answer is yes, you still need to decide whether requests should come from everyone or only from people you already share a server with.
| Goal | Friend-request setting to consider | Server DM setting to consider |
|---|---|---|
| No unsolicited contact from strangers | Deselect all friend-request options | Restrict direct messages from server members |
| Contact only through mutual communities | Allow Server Members | Keep server DMs available but monitored |
| Open to networking | Allow Everyone or Friends of Friends | Keep server DMs available |
| Temporary lockdown | Deselect all friend-request options | Restrict server DMs until the public post is old |
Discord provides direct-message permissions and friend-request controls.
Discord provides direct-message permissions and friend-request controls. Source
That sentence matters because it confirms the two channels are distinct. Do not assume that blocking friend requests also blocks messages sent from within a shared server.
Step 2: Set friend-request permissions
Friend requests can be allowed from Everyone, Friends of Friends and Server Members.
Friend requests can be allowed from Everyone, Friends of Friends and Server Members. Source
Each option has a different effect:
- Everyone lets any Discord user who knows your username send a request. This is the widest setting and the one most exposed by a public handle.
- Friends of Friends narrows requests to people connected through your existing friends. It reduces random requests but does not eliminate them.
- Server Members limits requests to people who share a server with you. This is useful when you want contact only inside communities you already moderate or belong to.
All three friend-request options can be deselected to stop incoming friend requests.
All three friend-request options can be deselected to stop incoming friend requests. Source
That is the correct interpretation: deselecting all three is the documented way to stop incoming friend requests. It does not delete existing friends, remove you from servers, or hide your username. It only changes whether new requests can arrive.
Step 3: Separate server DMs from friend requests
Server direct messages are messages sent from within a shared server, and they can arrive without a friend request. The friend-request controls above do not automatically cover them. Review the direct-message permission that applies to server members and decide whether it should stay open.
A practical rule: if you are publishing your username for a one-off reason, such as a portfolio or a public Q&A, restrict server DMs for the period when the post is most visible. If you rely on server DMs for community moderation or support, keep them available but treat unexpected messages as untrusted until the sender is verified through another channel.
Do not treat a restricted DM setting as account deletion or as a privacy guarantee. An edited or empty profile does not establish deletion of stored data, and permission changes do not remove messages already sent.
Step 4: Review what your public profile already reveals
Before you share the handle, open your own profile as a stranger would see it. Check the bio, linked accounts and any public server memberships that display your username. The goal is to reduce the number of places where the handle appears next to personal details.
For a deeper pass on profile visibility and connected accounts, see the Discord connections and profile privacy checklist. That guide covers a different layer: what your profile and connections expose, rather than who can send requests.
Step 5: After sharing, watch for impersonation
A public username is easier to copy than to hide. After you post it, watch for accounts that use a similar handle, the same avatar or a copied bio. Matching photos, biographies and handles cannot independently prove identity, so verify through a channel you already trust before acting on a message from an unfamiliar account.
If you need a structured way to document and respond to a copycat profile, the guide on protecting your username from impersonation covers the reporting and evidence steps.
Common mistakes
- Changing only one channel. Restricting friend requests while leaving server DMs open still allows contact from shared servers. Review both.
- Assuming a username becomes unsearchable. Permission changes control incoming contact, not discoverability. Your handle can still appear in searches, screenshots and server member lists.
- Deselecting options without checking the result. After changing friend-request settings, confirm the state of each option rather than assuming the change applied.
- Treating a restricted setting as deletion. Removing a contact path is not the same as deleting an account or stored data.
- Using an inaccessible recovery method during cleanup. If you are closing or cleaning an account, keep a recovery method you control until closure is complete.
- Trusting a matching profile. A similar handle or photo is a lead, not proof of who is behind an account.
Protecting your own footprint
Permission settings are one layer of a larger footprint. A username can appear in server member lists, quoted messages, screenshots and third-party directories that you do not control. No setting in this checklist makes your account hidden or your username unsearchable, and no tool can prove that a public match belongs to you.
If you want a structured way to review where a known public handle appears, TraceSeek is a username search app that checks 3,000+ platforms and returns a free first scan in 20-30 seconds. It reviews public matches; it does not change your Discord settings, restore accounts, expose private records or prove identity. Treat its results as leads to review, not as a complete account inventory.
Key facts
Discord provides direct-message permissions and friend-request controls.
Friend requests can be allowed from Everyone, Friends of Friends and Server Members.
All three friend-request options can be deselected to stop incoming friend requests.
TraceSeek checks 3,000+ platforms and offers a free first scan in 20-30 seconds.
Permission changes control incoming contact but do not make a username unsearchable or an account hidden.