Whitelist at connect
Checked the moment somebody joins, against their status, their faction and any open discipline. Approve someone in the dashboard and they are in within a minute.
QBox resource
It actually talks to your server
A versioned resource you install on your FiveM server, not a status embed. Your whitelist, your bans and your job grades live in the same place as your factions.
Identity linking
One code links a Discord account to every FiveM identifier a player presents. Identifiers are stored as a set, so swapping one does not shake off a ban.
Bans that sync both ways
Ban in Discord and they cannot connect. Ban in game and it is on their record with the reason and who issued it. One ban list, wherever it was written.
Player lookup from Discord
A slash command turns an identifier, a Discord user or a character name into the whole picture: factions, rank, duty history, discipline and past names.
Rank to job grade
Promote somebody in the dashboard and their in-game job grade follows. Rank, callsign and grade belong to the character, so a civilian character stays civilian.
In-game tablet
Their faction, their own record, documents and clock on or off, in game, with exactly the permissions they have on the web.
Be honest about the hard part
What happens when FiveHQ is unreachable
Your whitelist is the front door of your server, so the failure behaviour matters more than the feature list. This is exactly what the resource does.
- It defaults to fail-closedA whitelist that quietly opens during an outage is worse than a server that is briefly unreachable, because you notice the second one immediately and the first one three days later.
- Your regulars do not notice a blipPlayers the server has already checked keep getting in for about 20 minutes after their last check — an allow is cached for 5 minutes and stays usable for a further 15 during an outage. A deploy or a short wobble passes unnoticed.
- Somebody brand new is turned awayA player the server has never checked has nothing to remember them by, so they are refused and told to try again shortly. That is the trade fail-closed makes, and it is the right one for a whitelist.
- A known ban is still a banBans the server already knows about are enforced throughout an outage. They do not lapse because an API is down.
Connection, during an outage
- Played yesterday
- Allowed from cache
- First time joining
- Refused — try again shortly
- Banned last week
- Refused — ban still enforced
- Timeout budget
- 4000 ms
You can switch to fail-open if you would rather run an open server for an hour than a closed one. Most communities should not.
What is supported
QBox is what the resource is built and tested against today, on a live community. If you run something else, talk to us before you switch — we would rather tell you it is not ready than have you find out on a Friday night.
Rank, callsign and in-game job grade belong to the character, because QBox is multi-character. Discipline, bans and identifiers belong to the person. That split is what stops somebody dodging a suspension by switching character, while letting a department head keep their dashboard access while playing a civilian.
Put it on your server
The whole game integration is on the free plan. It is not the paywall and it never will be.