FiveM Whitelist: How to Set One Up (and Why You Need It)
Whitelisting is the single biggest lever on roleplay quality. It's the difference between a city where people build characters over months, and a server where someone spawns in, drives into a crowd, and logs off.
This guide covers the three whitelist models, how to implement one, and how to run applications without drowning your staff.
The three models
Open: anyone can connect. Best for early testing and casual servers — you get volume, but you also get everyone.
Application: players submit a character and get reviewed. This is the standard for serious RP and the reason the best cities feel consistent.
Paid or fast-track: applications are still reviewed, but supporters can skip the queue. Handle this carefully — sell the review speed, never a guaranteed approval.
- ✓ Launching and need players fast → open, then tighten later
- ✓ You want story-driven RP → application from day one
- ✓ Long review backlog → add a fast-track lane, keep the standard free lane open
How to implement it technically
Most servers gate connections at the identifier level. Your framework or a whitelist resource checks the connecting player's identifier (license, Discord ID, or Steam ID) against an allow list before letting them in.
The common setups: an ACE-permission based whitelist in your server config, a database-backed whitelist in ESX/QBCore, or a Discord-role bridge where holding a role in your Discord grants access. The Discord-role approach is popular because approving someone is a single role click.
Whatever you pick, make the deny message useful. "You are not whitelisted — apply at yoursite.com" converts a rejected connection into an applicant.
What to actually ask in the application
Keep it short enough to finish in one sitting, deep enough to filter out low effort. Five to seven questions is the sweet spot.
Ask for a character name and a short backstory, why they want to play here specifically, their understanding of one or two core rules (metagaming, powergaming, value of life), and a scenario question — "your character is robbed at gunpoint, what do they do?" Scenario answers separate real roleplayers from everyone else faster than any other question.
- ✓ Character name and short backstory
- ✓ Why this city, in their words
- ✓ Explain metagaming / powergaming / value of life
- ✓ One scenario question — the real filter
- ✓ Confirm they've read the rules
Running the queue without burning out staff
Set a published review window ("most applications reviewed within 48h") and stick to it — uncertainty is what makes applicants leave for another server.
Give reviewers a simple rubric with a fixed set of denial reasons, and always tell denied applicants whether they can reapply and when. A denied player who's told "reapply in 7 days with more detail" often comes back as one of your best roleplayers.
Move applications off Google Forms
Google Forms works, but it leaks: it's off-brand, it doesn't know who the player is, and approvals live in a spreadsheet disconnected from your server.
A branded application on your own site with Discord sign-in ties the applicant to a real identity, keeps the whole flow in your brand, and makes approvals a click instead of a copy-paste. You can set that up free with Mythara — including a fast-track option if you want one.
Run branded applications instead of Google Forms — free
Branded page, storefront, Discord login and a player passport — free to start.
Create your page — free →Frequently asked questions
Does whitelisting kill server growth?
It slows raw signups and raises retention. Serious RP players actively seek whitelisted servers because the barrier is what keeps quality high — the players you lose are usually the ones you wanted to filter.
Can I charge for whitelist access?
Many servers sell a fast-track review rather than access itself, which keeps a free path open for everyone. Whatever you do, run payments through Tebex per the Cfx Platform Agreement and never imply approval is guaranteed by paying.
How long should reviews take?
Publish a window and hold it — 24 to 48 hours is a good target. Predictability matters more than speed; applicants leave when they simply don't know.
Should I use Discord roles or a database whitelist?
Discord roles are simpler to operate (approve = grant a role) and match how RP communities already work. A database whitelist gives you finer control and survives Discord outages. Many servers run the Discord bridge and store the result in their database.