Treat a Linked Role tag as evidence of one thing: the server's administrators configured a connection requirement for that role, and the role grants access under those requirements. It is not a background check or an identity verification of someone's offline life. To inspect it, read the tag and the server's stated requirements, then stop there. If the requirements or your own connection controls are not visible, record that as unavailable and pause at the access boundary rather than inferring what an unseen requirement might mean.
Find public social profile clues with our TraceSeek app.
What the tag actually shows
A Linked Role tag lets a reader inspect the connection requirements chosen by that server's administrators, and the role grants access under those requirements. In plain terms, the server decided which external account must be linked before the role is granted, and the tag reflects that chosen rule. Calling that rule a background check overstates it. The role records a match between an account and a server requirement; it is not a statement about a person's history, character, or status away from the keyboard. [Discord Support: Connections and Linked Roles]
- Read the tag and the server's own stated requirements before drawing any conclusion.
- Describe what you see as a requirement match, not as verification of the person.
Separate server access from offline biography
Server access qualification and personal biography are different questions. Qualification answers whether an account satisfied a rule the moderators set. Biography covers who someone is outside that community, which is a separate matter from the server's access rule. Linking an external account requires authenticating to that account, but that is an account-level action, not a statement about the human being. [Discord Support: Connections and Linked Roles]
- Ask two separate questions: did this account meet the server rule, and what does that tell me about the person?
- Keep the second answer short: the tag does not settle it.
Visibility is a separate control
Profile visibility of the connection and of its details can be controlled separately, so a visible role tag and a visible connection profile are not the same setting. Someone can hide how a connection appears while still qualifying for a role. When you cannot see the underlying requirements, the honest result is unavailable, not a guess. [Discord Support: Connections and Linked Roles]
A comparison table for observers
Use a small table to keep observations, their limits, and the next step apart, so a visible detail is not quietly promoted into a conclusion.
| Observation | Limit | Next step |
|---|---|---|
| A role tag is displayed on an account | Shows the server configured a connection requirement for that role; not an identity or background check | Read the server's stated requirements and note them as access rules only |
| The connection profile is hidden | Visibility is controlled separately from qualification | Record unavailable; do not infer what the hidden connection contains |
| The connection details are visible | Shows the connection and its details were made visible on the profile | Treat as profile visibility, not as proof of who the person is offline |
When the control is not available
If the tag, the stated requirements, or your own connection settings are not visible to you, stop at that boundary. Note it as unavailable and look for current official help or ask for a voluntarily shared current state. Do not reconstruct the missing piece from assumptions or from what other servers happen to do.
- Write down exactly what you could not see.
- Ask for a voluntary current link or check official current help rather than guessing.
Your own connection controls
If you own the account, the relevant decision is about your own access, not about judging others. Removing a connection revokes Discord's future access and removes that connection's collected data according to the help article, so removal is a real change, not a cosmetic toggle. Hiding a connection is a different action from removing it. [Discord Support: Connections and Linked Roles]
- Before removing a connection, check which role it supports and whether you still need that access.
- Decide between hiding and removing deliberately; they have different effects.
A couple more questions
Does a Linked Role mean the server ran a background check on someone?
No. The tag reflects the connection requirements that server's administrators chose and that grant access under those requirements. That is access qualification, not an identity or background check of the person.
Can a person hide a connection and still have the role?
Yes. Profile visibility of the connection and of its details can be controlled separately, so qualification can persist while the connection is hidden from view.
What should I do if I cannot see the requirement behind a tag?
Record it as unavailable and stop at that boundary. Use official current help or ask for a voluntary current link rather than inferring what the hidden requirement is.
What does removing a connection change?
According to the help article, removing a connection revokes Discord's future access and removes that connection's collected data, so it is a substantive change rather than a display tweak.
Sources & editorial notes
Official references checked on October 23, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.