Save 20% with WELCOMEView sales
How to Connect txAdmin to Discord (2025 Guide)

How to Connect txAdmin to Discord: Status and Whitelist

What txAdmin’s Discord integration does

txAdmin is included with current FXServer builds and its native Discord integration can maintain a status embed and support Discord-member or Discord-role whitelisting. Create a dedicated Discord application, grant only the permissions the status channel needs, store the bot token only in txAdmin, and test the integration in a non-production guild or channel first.

  • Never paste the bot token into chat, screenshots, tickets or server.cfg.
  • Do not grant Discord Administrator permission when channel-level View, Send, Embed and History permissions are sufficient.
  • If the portal labels differ from this guide, follow Discord’s current Installation page and txAdmin’s current Settings → Discord fields.
  • Rotate the token immediately if it is exposed, then update txAdmin and re-test the status embed.

Goal: Enable txAdmin’s native Discord integration for status embeds and (optional) Discord‑backed whitelisting.

Works with any FXServer build that includes txAdmin. No third‑party hosting or bot framework required.

Prerequisites

  • A running FiveM server with txAdmin enabled (Settings → Global shows the panel is active).
  • Permission to create a Discord application in your Discord Developer Portal.
  • Developer Mode enabled in your Discord user settings (so you can copy Server/Channel/Role IDs).
  • The Guild (Server) ID and (optionally) a Channel ID where the bot is allowed to post.

Step 1 — Create the Discord Application & Bot

  1. Open the Discord Developer Portal and click New Application.
  2. Inside the application, go to Bot → Reset Token and copy the Bot Token. Keep it secret.
  3. On the same Bot page, enable SERVER MEMBERS INTENT. Save.

Tip: You don’t need the Presence or Message Content intents for txAdmin’s built‑in features.

Step 2 — Invite the Bot to Your Discord Server

  1. In the Discord Developer Portal, open Installation. Configure a server install link there; older portal layouts may show the equivalent OAuth2 URL Generator.
  2. Scopes: select bot and applications.commands (slash commands).
  3. Permissions: select View Channels, Send Messages, Embed Links, Read Message History.
  4. Use the install link to add the app to a test Discord server first, confirm the requested scopes and permissions, and only then install it in the production guild.

Keep permissions minimal. The bot only needs to read/post and embed.

Step 3 — Wire the Bot in txAdmin

  1. Open your txAdmin web panel.
  2. Go to Settings → Discord.
  3. Toggle Enable Discord Bot.
  4. Fill the fields:
    • Bot Token: paste the token from Step 1.
    • Guild ID: your Discord Server ID (right‑click server icon → Copy ID).
    • Announcements Channel ID (optional): a channel ID where txAdmin can post status/restart notices.
  5. Save.

Add the Live Status Embed

  • In your chosen Discord channel, type: /status add
  • txAdmin will post a persistent embed that auto‑updates with server info.

Customize the Status Embed (optional)

  • In txAdmin → Settings → Discord, open Change Embed JSON to edit title, description, fields, thumbnail, buttons/links, etc.

Step 4 — (Optional) Discord‑Backed Whitelist in txAdmin

You can gate server access by Discord membership or role.

  1. In txAdmin, go to Settings → Player Manager.
  2. Whitelist Mode: choose one of:
    • Discord Member – anyone in your Discord can join.
    • Discord Role – only members with specified role IDs can join.
  3. If using Discord Role, collect role IDs (Server Settings → Roles → right‑click role → Copy ID).
  4. Add the role IDs to the whitelist settings. Save.

Approve/Manage Requests:

  • Go to Player Manager → Whitelist to review requests and approvals.

Prefer role‑based whitelisting for better control. Update your Discord role assignment workflow accordingly.

Troubleshooting

  • Saving Discord settings times out → Ensure SERVER MEMBERS INTENT is enabled for your bot in the Discord Developer Portal.
  • Slash commands (/status, /info) don’t appear → Re‑invite the bot with the applications.commands scope; make sure it can see the channel.
  • Status doesn’t post/update → Verify channel permissions: the bot needs View Channel, Send Messages, Embed Links, Read Message History.
  • No messages from txAdmin → Double‑check the Guild ID/Channel ID values and that Developer Mode is enabled when copying IDs.
  • Noise in announcements channel → Leave Announcements Channel ID empty in Settings → Discord (txAdmin won’t auto‑post announcements).

Security Notes

  • Treat the Bot Token like a password. Rotate it if exposed.
  • Avoid granting Administrator or unnecessary permissions.
  • Restrict the bot to a single posting channel when possible.

Related Guides & Resources

Quick Checklist (Copy/Paste)

  • Bot created; SERVER MEMBERS INTENT enabled
  • Bot invited with bot + applications.commands scopes
  • Permissions: View, Send, Embed, Read History
  • Bot Token + Guild ID (and optional Channel ID) saved in txAdmin
  • /status add run in the target channel
  • (Optional) Whitelist Mode set to Discord Member/Role; role IDs saved

Practical checklist

Use this guide as a staging checklist before changing a live FiveM server. Confirm the current server artifact version, framework version, resource dependencies, database changes, and any client-side files before you apply the change.

  • Back up the affected configuration files and database tables.
  • Apply the change on a test server first.
  • Watch the server console and client F8 console for errors.
  • Check whether the change affects jobs, inventory, vehicles, maps, voice, permissions, or player data.
  • Document the exact file, command, or setting you changed so it can be reverted quickly.

Testing before production

After the first test, join with a normal player account and repeat the flow from the player perspective. If the topic involves performance, measure before and after with the same player count, route, and resource set. If it involves admin tools or permissions, verify both allowed and denied users.

Common mistakes

Most FiveM issues come from missing dependencies, stale cache, wrong folder names, framework mismatch, or configuration copied from another server. Avoid changing multiple systems at once; make one change, test it, and then continue.

Related resources

For production-ready assets, compare paid resources in the FiveMX shop. For free resources, browse free FiveM scripts and test each resource before using it publicly.

Production rollout notes

Before using this guidance on a live FiveM server, define the exact outcome you expect from the change. For How to Connect txAdmin to Discord, that means checking which resource, setting, command, or workflow is affected and confirming that the change fits your current framework, artifact version, and server rules. Keep the rollout small enough that you can reverse it quickly if players report errors.

Use a staging server with the same framework, database schema, resource order, and key dependencies as production. If the topic changes gameplay, permissions, visuals, voice, vehicles, maps, inventory, or economy behavior, test with at least one admin account and one normal player account. Watch server console output, client F8 logs, and resource timing while repeating the exact player flow that will happen on the live server.

Rollback checklist

  • Save the previous configuration file, resource folder, and database state before changing anything.
  • Record the resource version, commit, download page, or setting value you tested.
  • Restart only the affected resource first when possible, then restart the full server if dependencies require it.
  • If errors appear, revert the single changed resource or setting before testing another fix.

Maintenance guidance

Review this setup again after FiveM artifact updates, framework updates, or major resource changes. A configuration that works today can break after dependency updates, renamed exports, changed events, or database migrations. Keep notes with your server documentation so future admins understand what was changed, why it was changed, and how to verify it again.

Ongoing review

Recheck How to Connect txAdmin to Discord after major FiveM artifact updates, framework changes, or resource migrations. Confirm that the advice still matches current server behavior, that any linked source remains available, and that installation steps still match the files a server owner will actually download or configure.

For public servers, keep a short changelog beside your server documentation. Note what was tested, what changed, which accounts were used for verification, and how to roll back. This makes future maintenance faster and prevents old setup notes from becoming unclear or unsafe for players.

Official references and final verification

The official txAdmin documentation lists its Discord status embed and whitelist features. Discord’s app installation guide and OAuth2 and permissions reference explain current install links, scopes, bot permissions and token handling.

After saving txAdmin’s Discord settings, verify the bot appears only in the intended guild, the status embed updates, a normal member cannot run admin actions, an allowed role passes the optional whitelist, and a denied role remains blocked.