Discord /setup and the website
/setup in Discord and the dashboard on fiveunity.com are two doors into the same settings. Use whichever is closer to hand: a change made in one shows up in the other straight away.
Where: Dashboard → your server · In Discord: /setup
#One set of settings, two front doors
There is a single set of settings per Discord server, and both /setup and the website read and write it. If you set your staff log channel from the Discord panel, the Core page on the dashboard shows it as the current value; change it on the website and the next /setup panel shows the new one. Neither side has a copy that can drift out of date, and there is nothing to sync or publish.
Changes take effect immediately; there is no restart, no save-and-deploy step, and no waiting for the bot to pick them up.
/setup is the fastest way to stand a server up, because it can create the channels, categories and roles for you. The dashboard is better for everything after that: it shows every setting at once with your real channels and roles in the drop-downs, instead of one modal at a time.
#What only the website can do
Some features never had a Discord panel, and are configured on fiveunity.com only:
| Only on the website | Where |
|---|---|
| The embed builder: build a rich message with a live preview and save it as a reusable server template | Content → Embeds |
Custom commands: staff shortcuts like !transfer that post a canned reply | Content → Custom commands |
| Your community's documentation site: write pages, organise them, choose who can read and who can edit them | Content → Documentation |
| Protection: message filters, raid lockdown, anti-nuke and join-to-create voice | Safety → Protection |
| Slash command settings: turn a command off, restrict it to certain channels, add a cooldown, hide setup-only commands | Server setup → Slash commands |
Discord can still use what you build there: /embed post posts an embed template you built on the dashboard, and custom commands are typed in Discord even though they are written on the website.
#What only Discord can do
The dashboard configures; it does not operate. Every day-to-day action stays in Discord, where it belongs:
- Moderation:
/ban,/kick,/warn,/timeout,/purge,/blacklist. The dashboard shows the resulting history under Safety → Staff, and that view is read-only. The one exception is Safety → Moderation → Mass ban, for pasting a long list of IDs; it is Administrator-only, and every other moderation action stays in Discord. - Tickets:
/ticket(claim, rename, escalate, transcript, new, delete, and the rest). The website builds the panels and categories; staff work the tickets in Discord. - Roleplay:
/clock in,/clock out,/duty,/clock status,/gang,/rolerequest. - FiveM:
/player-info,/fivem-ban,/kick-id,/fivem-revive,/fivem-heal,/giveitem,/announce,/logs death,/logs vehicle,/logs inventory. - Roles and content in the moment:
/role,/temprole,/selfroles,/echo,/poll,/giveaway,/translate.
A few jobs work from either side, because both are useful: backups (/backup or Server setup → Backups), and re-syncing the command menu (/refresh or Re-sync slash commands).
See How commands work for the full list.
#Secrets are write-only on the website
Anything sensitive can be set or replaced on the dashboard, but is never shown again, not to you, not to another admin, not on a page reload. The dashboard only ever tells you whether one is stored.
| Secret | Where you set it | What you see afterwards |
|---|---|---|
| Tebex secret key | Server setup → Core → Tebex | The field shows "Stored (type to replace)" and the hint "Currently set. Write-only, never shown again." |
| FiveM bridge keys | Roleplay → FiveM | New keys are displayed once, at the moment you generate or rotate them. Reloading the page never shows them again. |
| txAdmin password | Roleplay → FiveM | Write-only; the panel confirms the credentials are saved but never returns the password. |
| Google Gemini key for the AI Assistant | Support desk → AI Assistant | The field shows •••••••• (saved). Type a new key to replace it. |
Copy a FiveM bridge key into your server configuration as soon as it is shown. If you lose it, there is no way to read it back; you have to rotate the key, which invalidates the old one and means updating the resource again.
Because they are write-only, handing over to a new administrator is safe: they can replace a key without ever seeing the old one, and a leaked key is fixed by pasting a new one over the top.
#Which to use when
| Task | Best door |
|---|---|
| Brand-new server, nothing exists yet | /setup; it creates channels, categories and roles for you |
| Changing a channel, role or toggle | Dashboard; everything visible at once, with real drop-downs |
| Building or editing a ticket panel, form or embed | Dashboard |
| Moderating, running tickets, roleplay commands | Discord |
| Reading what a setting is currently set to | Either; /setup panels show a status summary per module |