To connect txAdmin to Discord, create a dedicated Discord application and bot, invite it to the correct server with only the permissions it needs, copy the bot token into txAdmin’s Discord settings, and configure status messages and role-based access as separate features. Keep the token private: it authenticates the bot and should never appear in screenshots, client files or a public repository.
Reviewed 12 August 2026 against the official Cfx.re txAdmin documentation, Discord’s application setup y OAuth2 documentation. Labels can move between txAdmin releases, so use the settings shown by your installed version.
Separate the four moving parts
| Part | Objetivo | Typical failure |
|---|---|---|
| Discord application and bot | Identity used by txAdmin | Wrong application, disabled bot or regenerated token |
| Server status | Publishes or updates status in a chosen channel | Wrong channel or missing view/send/embed permissions |
| Roles or whitelist | Maps Discord membership/roles to the configured access rule | Wrong server/role ID, role hierarchy or member intent requirement |
| txAdmin permissions | Controls who may administer the FiveM server | Discord role assumed to grant txAdmin rights automatically |
Do not debug these as one feature. First prove that the bot is online, then prove it can access one channel, then add status behavior, and only then test optional role or whitelist logic.
Step 1: create a dedicated Discord application
- Open the Discord Developer Portal and create a new application for this server.
- Add a bot to the application.
- Give it a clear name so staff can distinguish Production from staging.
- Generate or reset the token only when you are ready to store it securely.
A bot token is a secret, not an application ID or public key. If it is exposed, reset it in Discord and update txAdmin immediately. Store the replacement only in the server-side setting intended for the token.
Step 2: invite the bot with minimal permissions
Use Discord’s OAuth2 installation flow for the application and select the bot scope required by the current setup. Start with the smallest channel permissions that satisfy the feature: view the selected channel, send messages, embed links and read message history where status updating needs it. Avoid Administrator unless the official integration explicitly requires it and you have reviewed why.
Restrict the bot to a dedicated status or administration channel where practical. After inviting it, confirm it appears in the intended Discord server. Being listed as offline is expected until txAdmin successfully logs in with the token.
Step 3: configure the bot in txAdmin
Open txAdmin as an authorized administrator and locate the Discord integration settings in your installed release. Paste the token into the token field without quotes or extra whitespace. Select the intended Discord server and channel using the inputs txAdmin provides. Save, then restart only the component or server if the interface requests it.
If you are building the FiveM side from scratch, use the FiveM server setup path first. Discord cannot repair an unhealthy FXServer or an unreachable txAdmin instance.
Configure status messages separately
Enable the status feature and select a channel where the bot can post. Start with a plain test update before adding custom wording or embeds. Confirm that the message changes when the FiveM server starts, stops or changes player count according to the behavior documented by your txAdmin version.
If the bot logs in but no status appears, check the selected channel ID and channel-specific overrides. A server-wide role may allow sending while a channel override denies it. Also inspect txAdmin’s console/log output for the Discord API response rather than repeatedly regenerating the token.
Configure roles or whitelist rules separately
Role-based access requires the exact Discord server and role identifiers expected by the integration. Enable Discord’s developer mode to copy IDs when the current setup asks for them. Role names are not stable identifiers and two roles may share a similar name.
Test with one account that has the required role and one that does not. Remove and re-add the role, reconnect, and confirm when the integration refreshes membership. Do not assume a Discord role automatically grants txAdmin administrator permissions; txAdmin’s own permission model remains a separate control unless the documented feature explicitly maps them.
Protect the token and permission boundary
- Never paste the token into Discord chat, a support ticket visible to others or a client-side resource.
- Do not commit it to Git or store it in a public screenshot.
- Limit access to both the Discord Developer Portal application and txAdmin settings.
- Reset the token after exposure or when an administrator with access leaves.
- Review the bot’s server and channel permissions periodically.
Troubleshooting checklist
| Síntoma | Controlar |
|---|---|
| Bot stays offline | Token belongs to the correct bot, contains no whitespace, has not been reset, and txAdmin logs show a login attempt |
| Bot is online but cannot post | Selected channel, view/send/embed permissions and channel overrides |
| Status never updates | Status feature enabled, correct channel, txAdmin/FXServer state and integration log |
| Role member is rejected | Correct server/role ID, role actually assigned, refresh/reconnect behavior and any required member intent |
| Unauthorized member is accepted | Fallback access rules, multiple allowed roles and server-side permission configuration |
| It stopped after a token reset | txAdmin still has the old token; save the new one and restart as required |
Final verification
- Bot logs in after a clean restart without token errors.
- Status posts only in the intended channel.
- The minimum bot role can update the message without broader server privileges.
- The allowed test user passes the role/whitelist rule.
- The unallowed test user fails the same rule.
- Neither Discord access nor a hidden UI button bypasses txAdmin’s own administrator permissions.
Once these checks pass independently, the integration is easier to maintain: one bot identity, one protected secret, narrowly scoped channel access and explicit rules for status, whitelist and administration.