🛡️Permissions

Permission groups decide which of your Discord roles may use which FiveUnity commands and features. A group is a list of roles plus a list of permissions; anyone holding one of those roles may use everything the group lists. Out of the box FiveUnity offers an eight-step ladder (Support up to Owner) that you attach your own roles to.

#How a permission check works

Every time someone runs a command or presses a staff button, the bot asks three questions in order:

1. Is this the server owner? The owner can always do everything.
2. Does the member have Discord's Administrator permission? Administrators can always do everything.
3. Otherwise: does the member hold a role that is in a permission group which lists that permission?

If none of those is true the member gets "You do not have permission to use this command."

Some commands are open to every member and skip the check entirely, because they are how people use the bot day to day: /help, /apply, /suggest, /store, /leaderboard, /myassets, /docs, /ping, /clock in, /clock out, /clock status, /gang, /rolerequest, /vouch, /ai ask, /logs stafflogs, /redeem and /subscription. They still check their own settings: /apply needs an open application, /suggest needs the suggestion channel, /vouch needs the vouch role you configured (staff only until you set one), /ai ask needs an admin to switch it on, /logs stafflogs answers only the server owner and the viewers they picked, and /redeem insists on the owner or an Administrator.

This sits on top of Discord's own rules, it does not replace them. Commands such as /ban, /purge or /setup also declare a required Discord permission, and Discord hides or blocks them for members who do not have it before the bot is ever asked. You can adjust those in Server Settings → Integrations → FiveUnity in Discord.

#What a group can be granted

The Permissions page lists every permission the bot has, grouped by category, each with a one-line description. Tick what a group may use:

Granting a command always covers its subcommands, so gang-admin covers gang-admin.reset-cooldown. A few subcommands deliberately sit under a different permission: /ticket summary checks ai.summary, so granting ticket does not hand out AI summaries; you grant ai. See AI Assistant.

One thing no group can grant: who may search the staff logs. That list belongs to the server owner alone, and Discord Administrator does not bypass it.

Commands that Discord also restricts show a small needs … tag (for example needs Ban Members): the member must have that Discord permission as well, or Discord never shows them the command.

#The default ladder

Load defaults creates eight groups. Each step includes everything below it, so you only have to think about where a role belongs:

All bridge, txAdmin, gameplay-log and vouch-setup commands live in the FiveM permission category. The default ladder gives that category only to Management and above. Loading defaults removes those FiveM permissions from its lower default groups if an older setup had put them there; it does not touch custom groups.

#The owner-only commands

Two commands are not on the ladder and cannot be granted to any group, not even one holding *. They check who owns the Discord server and refuse everyone else, Administrators included:

If either appears on one of the eight default groups from an older setup, Load defaults takes it back off. Ownership follows the Discord server: transfer the server and the new owner gets both commands.

Apart from that FiveM security floor, loading defaults only ever adds. It never removes another permission you took out, and it never touches the roles on a group, so it is safe to re-run after a FiveUnity update to pick up new commands. It does not assign any roles for you: a fresh group starts empty and grants nothing until you add roles to it. Older default groups are renamed in place, keeping their roles and permissions: Administrator becomes Admin, Senior Administrator becomes Senior Admin, and Head Administrator becomes Head Admin.

The Permissions page can show the full ladder before you load it (Show the default ladder), with every permission each step adds.

#Set it up

1. Go to Dashboard → Server setup → Permissions.
2. Press Load defaults to create the ladder.
3. Open a group, pick the Discord Roles that belong on that step, and press Save.
4. Untick or tick individual permissions if the defaults are not quite what you want, then Save again. Unsaved edits are flagged on the group until you save or discard them.

To build your own group instead, type a name into New group name and press Create group, then add roles and tick permissions the same way. Delete removes a group after a confirmation; the Discord roles themselves are untouched.

#Settings

Saving a group takes effect immediately, no re-sync, no restart.

#Groups also define "staff"

Being in any permission group is what makes someone staff to the rest of the bot, alongside the owner and Administrators. That matters for the buttons FiveUnity posts, which are not commands. Each staff button checks the permission of the command that does the same thing: claiming a ticket checks claim, deleting one checks delete-ticket, saving a transcript checks transcript, escalating checks escalate, accepting or denying an application checks applications, approving a role request checks rolerequests, Mark as Processed on a Tebex purchase checks tebex. Searching Tebex purchase logs through /logs find or Ask the logs also needs tebex; without it those channels stay out of the search even when Log Lookup indexes them. On the default ladder, Senior Admin holds both tebex and logs.find so store operators can mass-search gameplay and purchase logs for abuse without Management. The page arrows on log embeds work for whoever ran the search.

Configuration panels opened from /setup need the setup permission, except the panels of a command that has its own permission: the log lookup panel checks logsetup, the txAdmin dashboard refresh checks dashboard, the keyword defaults picker checks keyword, the queue panel checks queue, the linked-server panel checks linked-server, and the Tebex panels check tebex. Editing permission groups from Discord needs permissions, so a Head Admin with setup cannot quietly hand themselves *.

Two things are not decided by permission groups. Who can open the dashboard is Discord's Administrator or Manage Server permission, and who can edit your documentation site is set page by page under Dashboard → Content → Documentation → Page permissions.

#In Discord

Run /setup and press Manage Permissions. The panel gives you Load Defaults, Create Group, Delete Group and View Commands, plus a dropdown listing every group with its role and permission counts so you can edit one. Adding permissions in Discord works by category and lists whole commands; for subcommands and the descriptions, use the dashboard. It is the same data in both places, so changes made in either show up in the other straight away.

#Tips

#Related

• Slash commands: turn commands off, restrict them to channels, add cooldowns.
• Core settings: the Staff and Admin roles used elsewhere in the bot.
• How commands work
• Discord /setup and the website