A whitelist decides who may join your FiveM server. In txAdmin, this feature is now called Allowlist, both terms appear in the code and in the Discord commands. This guide shows you which mode fits your project, how to set it up, and how to build an application process that is fair and only collects the necessary data. Status: October 2026, txAdmin 8.1.x.
Short answer: which mode fits your server?
txAdmin comes with six modes. You can find them under Settings → Allowlist in the field “Allowlist Mode”.
| Mode in txAdmin | What gets checked | Suitable for |
|---|---|---|
| Disabled | Bans only (if enabled) | Public servers without application |
| Admin-only (maintenance mode) | fivem:– or discord:-Identifier belongs to a txAdmin admin |
Maintenance, setup phase, internal tests |
| Discord Server Member | Player is a member of your Discord server | Semi-open servers that only require joining a Discord |
| Discord Server Roles | Player is a member and has at least one of the configured roles | Classic RP whitelist with application |
| Approved License | license:-Identifier was approved by an admin |
Projects without Discord linking or with manual approval per player |
| External Allowlist Resource | txAdmin checks nothing, your own resource decides | Own systems, e.g. an application portal with a database |
For most German RP servers, this is Discord Server Roles the pragmatic choice: applications already run through Discord, and approval is a single click on a role. If you want no barrier at all, look at how Server without whitelist work.
Prerequisite: server and txAdmin are running
Before you touch the allowlist, your server should start cleanly via txAdmin. If you are still at the beginning, the guide will help you Create a FiveM server. Important: The convars sv_appearAllowlisted and sv_allowlistInstructions sets up txAdmin itself. If they are listed in your server.cfg, txAdmin comments them out because the settings page overrides them. So don't enter them manually.
If any mode other than "Disabled" is active, the server list shows a padlock icon next to your server name.
Step by step: setting up the modes in txAdmin
Admin-only (maintenance mode)
- Open Settings → Allowlist and select "Admin-only (maintenance mode)".
- Check in the Admin Manager that every team member has their FiveM or Discord ID stored. Without one of these IDs, even an admin can't get in.
- Save. txAdmin checks the allowlist on every connection attempt.
Approved License
- Choose the "Approved License" mode.
- Fill in the "Allowlist Instructions" field (required, maximum 512 characters). The text appears on the server side in the client and in the rejection message, e.g. "Apply in our Discord in the #bewerbung channel and state your whitelist ID."
- When a player tries to join, txAdmin automatically creates a request with an ID in the format
R1234on and shows it to the player as a "Whitelist ID". - Under Allowlist In the navigation, the left side shows open requests (approve, deny, or deny all), and the right side shows already approved players who haven't joined yet. You can also pre-approve players via "Add Approval".
Alternatively, approval works via a Discord bot: /allowlist request with the request ID or /allowlist member with a Discord member (the older command /whitelist was added to /allowlist renamed and only replies with a notice about it). The command only works if your Discord account in txAdmin belongs to an admin with the permission players.whitelist is assigned to.
Discord Server Member and Discord Server Roles
Both modes can only be selected once the Discord bot is active in the Discord tab. Bot setup follows in the next section. Then:
- Select “Discord Server Member” or “Discord Server Roles.”
- Fill in "Allowlist Instructions", for example with a link to Discord and a note about the application.
- Roles only: Under "Allowlisted Discord Roles" enter the role IDs, separated by commas if there are several. It is enough if the player has one of them.
External Allowlist Resource
Here txAdmin skips the allowlist check entirely (it still checks bans if enabled). Your own resource must then reject connections itself. This is only worthwhile if you already run your own application or account system.
Setting up the Discord bot: bot, server ID, role IDs
This guide uses the bot built into txAdmin.
- Im Discord Developer Portal Create an application and build a bot. Copy the token and keep it safe; it doesn't belong anywhere public.
- For the bot, enable the privileged intent Server Members enable it. txAdmin requires it explicitly. If it's missing, the bot start fails with a message saying a required privileged intent is missing.
- Invite the bot to your Discord server.
- In Discord, go to Settings → Advanced and enable Developer Mode. Then you can right-click to copy the server ID, and under Server Settings → Roles copy the ID of each role.
- In txAdmin, under Settings → Discord Enable the bot, enter the “Token” and “Guild/Server ID,” then save.
- Go back to the allowlist and enable role mode with the copied role IDs.
It's best to create a dedicated role such as "Whitelisted" instead of reusing existing roles like "Member". That way, if someone breaks the rules, you can remove just that one role without touching the rest of their Discord permissions.
Design the application process
The technical setup takes half an hour. What shapes your server is the process behind it. How that looks from the player's side is described in the article on Whitelist application. From the operator's perspective, these points have proven useful:
Questions
- A few targeted questions instead of long forms: RP experience, a short character idea, two or three scenario questions about your rules.
- Ask about rules that really matter, such as Fear RP or metagaming. For that you need a clear Rules and regulations.
- No minimum word count. Long texts say little about good roleplay.
Review
- At least two team members review each application using a short checklist, so decisions stay comparable.
- Set a processing time and communicate it, e.g. „within 72 hours“.
- Optional: a short voice chat on Discord for borderline cases.
Rejection
- A brief justification, one concrete suggestion for improvement, and a fixed waiting period before the next application.
- No public rejections in the channel. Send them via direct message or ticket.
Data minimization (GDPR)
Only ask for what you need for the decision. For an RP whitelist, that is usually the Discord name, age only as "at least X years old: yes/no", and the answers to the content questions. You don't need real names, place of residence, photos or ID details. Define who may see the applications and when they are deleted, for example about 30 days after the decision. This follows the data minimization principle of Art. 5 GDPR. For detailed legal questions, consult a specialist, not this guide.
Common problems and solutions
Player isn't recognized even though they have the role
The Discord modes require the discord:-identifier. According to the txAdmin message, the player needs the Discord app open for this; the web version is not supported. Solution: open the Discord app, restart FiveM, and reconnect. If the player can't get in right after joining Discord, wait a moment and try again, because txAdmin caches its member list.
Identifier doesn't match
In “Approved License” mode, the license:-identifier, i.e. the license tied to the Rockstar account. Anyone who starts with a different Rockstar account gets a new request ID. It's better to approve the new request than to search for old entries. If the license is missing entirely, the server is probably running with sv_lan true. This disables the license check and removes the server from the public list. For a live server, this belongs on false.
Bot not running or Discord modes greyed out
Greyed-out options mean the bot is not enabled in the Discord tab. If it doesn't start, check the token, server ID, and the Server Members intent. txAdmin already rejects role IDs in the wrong format when saving. A formally valid but incorrect ID (e.g. from a different Discord) only shows up when joining.
Admins can't join during maintenance mode
The FiveM or Discord ID of the account is missing in the Admin Manager. Add it, save, and reconnect.
Additional notes on setting up the Discord bot
These details supplement the section above:
- New applications in the Discord Developer Portal automatically come with a bot user; an "Add Bot" button is no longer needed. Generate the token with "Reset Token" and copy it immediately, because Discord won't show it again later. Treat it like a password and never share it publicly.
- The bot needs no permissions beyond reading members and roles; permissions like “Manage Roles” aren't required for the allowlist.
- Test the setup by connecting once with the whitelist role and once without it. The player needs the
discord:-identifier, i.e. an open Discord app. A new role takes effect on the next connection attempt; a server restart is not necessary.
There are also separate whitelist resources. According to the GitHub repository, the free version of "DiscordWhitelist" by FAXES is no longer maintained. For most servers, the built-in txAdmin allowlist is the better choice.
FAQ
Can I combine Discord roles and Approved License?
No, txAdmin always checks exactly one mode. If you want both, use „External Allowlist Resource“ with your own logic.
Where do I set the message for rejected players?
In the "Allowlist Instructions" field under Settings → Allowlist. The text appears in the rejection message and on the server side in the FiveM server list.
Does the server need to restart after assigning a role?
No. The check runs on every connection attempt. If the player has the role, they can join on their next connect.
Can I connect the whitelist with my own scripts?
Yes. txAdmin sends server events such as txAdmin:events:whitelistRequest, txAdmin:events:whitelistPlayer and txAdmin:events:whitelistPreApproval. This lets you, for example, report new requests to a team channel. The fields are located in the txAdmin Event Documentation.




