What retiring an invite actually does
A Discord invite is a code that lets someone join a server. Retiring an old one means removing that code so it can no longer be used. This is a link-level action, not a membership action.
Two things stay the same after you delete an invite:
- Members who already joined remain members. Their access is governed by roles and channel permissions, not by the invite they used.
- Server content is not erased. Deleting an invite does not delete messages, channels, or files.
If your goal is to stop new people from using a leaked link while keeping the current community intact, deleting the invite is the relevant step. If your goal is to remove a specific person, that is a separate moderation action.
Before you remove the link: audit first
Deleting an invite does nothing about copies that already exist elsewhere. Before removal, take stock of where the old link may still be visible.
| Check | Why it matters | What to do |
|---|---|---|
| Public profiles and bios | A copied invite can sit in a bio for months | Note the platforms and update or remove the link |
| Pinned messages and old announcements | Links persist long after the event | Edit or delete the message that contains it |
| Wikis, forums, and link lists | Third-party pages may still point to it | Request an update where you control the page; otherwise treat the link as still public |
| Screenshots and reposts | You cannot recall an image someone saved | Assume the code may circulate even after deletion |
| Your own permissions | Not every member can manage invites | Confirm you have the required server permissions before starting |
This audit is about reducing exposure, not achieving certainty. You cannot guarantee that every copy of a link has been found or removed.
Check permissions before you act
Invite management is permission-gated. If you are not the server owner or do not hold a role that can manage invites, you may not see the option or may not be able to complete the removal. Confirm your role before planning the change, and coordinate with whoever holds the necessary permissions so the action is not half-finished.
People with the required server permissions can remove generated invites from Server Settings, Invites. Source
Step-by-step: retire the invite
- Confirm your role can manage invites.
- Record the current state — which invite codes exist, which channels they point to, and whether any are still in active use.
- Decide the replacement path, if any. If new members should still be able to join, create a fresh invite with settings you are comfortable with and update your public links to it.
- Delete the old invite from Server Settings, Invites.
- Update the places you found in your audit so they point to the new link or to nothing.
- Verify that the old code no longer works and that existing members can still reach the channels their roles allow.
Invite settings let you control how long a link lasts and how many times it can be used, which is useful when you create the replacement.
Discord invite settings include link duration and maximum uses. Source
What deletion cannot do
Set expectations before you promise anything to your community:
- It does not remove members. People who already joined stay until they leave or are removed through moderation.
- It does not change permissions. Roles and channel access are separate from invite codes.
- It does not erase content. Messages, media, and channel history remain.
- It does not guarantee the link is gone from the internet. Copies in screenshots, archives, or pages you do not control may persist.
- It is not reversible.
A deleted invite code cannot be recreated, including by Discord Support; pausing invites is a separate option. Source
If you want to stop new joins temporarily without deleting the code, pausing invites is a separate option from deletion. Choose deliberately: pausing preserves the code for later, while deletion ends it permanently.
A short before/after checklist
Before
- Confirmed you have permission to manage invites
- Listed active invite codes and where each one is published
- Checked bios, pinned messages, announcements, and third-party pages
- Decided whether a replacement invite is needed and with what duration and use limit
- Told moderators or co-owners what will change
After
- Old code deleted and confirmed unusable
- Public links updated to the new code or removed
- Existing members confirmed able to reach the channels their roles allow
- Community informed that membership and content were not affected
- Any remaining public copies noted as outside your control
When a username check is relevant — and when it is not
If the old invite was shared alongside a public username, you may want to see where that username appears publicly. TraceSeek is an optional app that checks a known public username across 3,000+ platforms; the first scan is free and takes 20–30 seconds. It cannot delete invites, change server settings, or remove members, and a public match is a lead rather than proof of who owns an account. It also cannot discover renamed accounts or search username variants automatically.
For the server itself, the work stays inside Discord: audit, permissions, deletion, and updating the places you control.