A Discord role allowlist lets staff approve access by assigning a specific role. Use the Discord-role mode built into your installed txAdmin version, then test both an approved and an unapproved account before relying on it.
Prepare access and recovery
You need permission to configure txAdmin and the Discord application, plus a Discord server and a dedicated approval role. Keep an authorized txAdmin recovery login available. Do not combine several allowlist scripts until you understand which one accepts or rejects a connection.
1. Connect the Discord bot
Set up the dedicated bot through txAdmin’s Discord integration. Follow the integration’s displayed requirements for bot permissions and member intents. Store its token only in the protected server-side setting. If a token appears in a screenshot or public repository, reset it and update the integration.
Confirm the bot connects to the intended Discord server before configuring access. Channel status messages and connection approval are separate features; a working status message does not prove the allowlist works.
2. Copy the server and role IDs
Enable Developer Mode in Discord’s advanced user settings. Copy the server ID and the ID of your approval role. Use IDs, not display names. Assign the role to one test member and leave another member without it. Keep permission to assign that role limited to staff who may approve access.
3. Select the Discord-role mode
In txAdmin’s allowlist settings, select the mode for Discord roles and enter the required server/role IDs. The upstream configuration calls this mode discordRoles; use the interface provided by your installed version instead of editing unrelated resource files. Save the setting and follow any restart instruction shown.
Write a short rejection message explaining where to apply and how to get help. Avoid exposing internal staff channels, tokens or personal identifiers in connection messages.
4. Test the complete decision
- Connect with the member who has the approval role. Confirm the server accepts the connection.
- Connect with the member who lacks the role. Confirm rejection and a useful message.
- Remove the role from the approved member, allow for the integration’s documented refresh behavior, then reconnect and confirm rejection.
- Reassign the role and reconnect. Check the approved case again.
- Review logs and recovery behavior when Discord membership cannot be resolved. Do not assume that a dependency failure has the desired access behavior.
Troubleshoot the failed boundary
If the bot cannot connect, inspect the token, selected application and txAdmin log. If only role checks fail, verify the guild ID, role ID, actual membership and configured mode. Follow txAdmin’s current guidance for Discord identity detection; a missing identifier should produce an actionable rejection.
Do not add Administrator permission or restart repeatedly as a substitute for reading the error. If a separate allowlist resource is installed, disable the conflicting policy only during a controlled maintenance change and verify access again.
Maintain the rule
Document who grants the role, how appeals work and how access is removed. Review bot and staff permissions when administrators change. A role allowing gameplay should not automatically grant txAdmin administration rights.
Reference documentation
Source: raw.githubusercontent.com · Cfx.re — txAdmin · Source: docs.discord.com