Allowlisting & access
Choose who can connect and help rejected players take the next step.
Some txAdmin versions call this feature whitelisting; current source labels it allowlisting. Permission and event names can still contain whitelist.
Choose the mode
The current configuration schema supports:
| Mode | Meaning |
|---|---|
disabled | No txAdmin allowlist restriction |
adminOnly | Access restricted to admins |
approvedLicense | Player license must be approved |
discordMember | Player must be a member of the configured Discord server |
discordRoles | Player must have an allowed Discord role |
external | Access is handled by an external integration |
Use the panel settings and player/allowlist pages to configure access. Discord modes need a working bot configuration and the relevant player Discord identity. External mode requires your external integration to be working; it is not an automatic approval system.
License approval workflow
A rejected player may receive a request ID. Ask them to send that ID through your server’s support process, review the request, then approve or deny it in the panel. Authorized staff can also use the bot’s /whitelist command where configured.
Write a useful rejection message
Include your actual support URL, which information the player should provide, and whether approval is manual or based on a role. Avoid the default example Discord link. Do not promise that rejoining Discord always solves the problem; check the selected mode and player identity.
Test both outcomes
Verify with one eligible player and one ineligible player. Confirm that the approved player can join and that the rejected player sees useful instructions. Do not treat a configured role ID as proof that the bot can read the guild member.
Developer integrations can use the allowlist events but should not rely on events as a durable database feed.
Source: txAdmin upstream documentation.