FeaturesPricingIntegrationsCommunityAboutDocs

Docs / FiveM / Whitelist Sync

Whitelist Sync

When a whitelist application is approved in Docket, the player is automatically whitelisted on your FiveM server. No manual entry, no spreadsheets, no copy-paste.

How it works

The sync flow works like this:

  1. A member submits a whitelist application via Discord (/apply new whitelist or /whitelist apply)
  2. Staff approve the application in Discord or from the dashboard
  3. Docket looks up the member's Discord ID and passes it to the docket-fivem resource running on your game server
  4. The resource grants the player whitelist access using your framework's permission system
  5. The next time that player connects, they are allowed in

Player identification

Docket identifies players by their Discord ID. Your FiveM server must have Discord identifiers enabled in server.cfg. This is on by default for most setups, but verify with:

# In server.cfg
set sv_authMaxVariance 1
set sv_authMinTrust 5

When a player connects, FiveM provides their Discord ID (formatted as discord:123456789) which the resource matches against the Docket-approved whitelist.

Framework-specific behavior

FrameworkHow whitelist is granted
QB-CoreSets player permission level to 'allowed' in the players table.
vMenuAdds the player's Discord ID to the vMenu whitelist ACE permission group.
ESXSets the player's group to 'user' in the users table (disabling guest/banned status).
CustomCalls the configurable export: exports['docket-fivem']:onWhitelistApproved(discordId).

Denial sync

When an application is denied, the player's Discord ID is not added to any whitelist. If they were previously whitelisted (from an earlier approved application that was later revoked via the dashboard), their access is removed on the next server restart or when they next attempt to connect.

← QB-Core SetupRoblox Integration →