Admin Whitelisting
Admin whitelisting allows server admins to bypass certain anti-cheat checks. This is useful if you have in-game admin tools that would trigger detections.
Security Notice
Only whitelist trusted admins. Whitelisted players can bypass most anti-cheat protections, so careful management of the admin list is essential for maintaining server security.
Configuration Methods
FiniAC supports three methods for whitelisting admins, offering flexibility for different server setups.
Method 1: Direct Identifiers
Add admin identifiers directly in the FiniAC config. This is the simplest method and is recommended for small servers with a few admins.
Steps:
- Navigate to the Config page on the FiniAC web panel
- Find the "Admin identifier list" option
- Add your admin identifiers to the list
Supported identifier formats:
- Full format:
discord:123456789012345678,fivem:1234567,steam:110000123456789 - Value only:
123456789012345678,1234567,110000123456789
Example configuration:
discord:123456789012345678
fivem:1234567
steam:110000123456789
license:1234567890abcdef1234567890abcdef12345678Or using value-only format:
123456789012345678
1234567
110000123456789
1234567890abcdef1234567890abcdef12345678Mixed Formats
You can mix full format and value-only format in the same list. FiniAC will automatically recognize both.
Method 2: ACE Permissions
Use FiveM's native ACE permission system to automatically integrate FiniAC with your existing server permissions. This method is recommended for medium to large servers with established permission systems.
Understanding ACE Permissions
ACE permissions work with principals (identifiers that hold permissions) and groups (collections of principals). You can grant permissions to groups and then add players to those groups, or grant permissions directly to player identifiers.
Basic Setup:
- Grant the admin group the FiniAC permission in your
server.cfg:
# Grant finiac permission to the admin group
add_ace group.admin finiac allow- Add the ACE permission to FiniAC config's "Admin identifier list":
ace:finiacACE Prefix Required
When adding ACE permissions to the FiniAC config, you must prepend the permission name with ace:. For example, the ACE permission finiac becomes ace:finiac in the config.
ACE Permission Examples:
Example 1: Single Admin Group
# Grant finiac permission to admin group
add_ace group.admin finiac allow
# Your existing config, where users are added to the admin group
add_principal identifier.discord:123456789012345678 group.admin
add_principal identifier.discord:987654321098765432 group.admin
add_principal identifier.steam:110000123456789 group.adminFiniAC config:
ace:finiacExample 2: Multiple Staff Levels with Inheritance
# Your existing hierarchy is probably similar to this: moderators → admins → owners
add_principal group.admin group.moderator
add_principal group.owner group.admin
# Grant finiac permission to moderators (inherited by admins and owners)
add_ace group.moderator finiac allow
# Add players to their respective groups
add_principal identifier.discord:111111111111111111 group.owner
add_principal identifier.discord:222222222222222222 group.admin
add_principal identifier.discord:333333333333333333 group.moderatorFiniAC config:
ace:finiacMethod 3: txAdmin Automatic Whitelisting
Players with txAdmin access are automatically added as admins on FiniAC.
Requirements:
- txAdmin version v6.0.1 or newer
- Player must be logged into txAdmin
How it works:
- Players who can access txAdmin are automatically considered admins
- No additional configuration needed
- Works automatically when players are authenticated with txAdmin
Best Practices
Do:
- Use ACE permissions for large staff teams (easier to manage)
- Regularly review and update the admin list
- Remove admins who no longer need access
- Use full identifier format (eg.
discord:123456789012345678)
Don't:
- Share admin identifiers publicly
- Whitelist players who aren't fully trusted
- Forget to remove former staff members from the list