Groups

Similar to permissions, groups are managed via ACEs and can be checked using the native IS_PLAYER_ACE_ALLOWED or the export from fxManager resource: exports.fxmanager:hasGroup(source, groupName).

How to use the groups

Two options are offered to check groups:

1. Using the native IS_PLAYER_ACE_ALLOWED
2. Using the export from fxManager resource: exports.fxmanager:hasGroup(source, groupName)
   • source: string | number
   • groupName: string

Code example:

-- using the export
local hasGroup = exports.fxmanager:hasGroup(source, "moderator")

-- using the native
local hasGroup = IsPlayerAceAllowed(source, "fxmanager.groups.moderator")

Here is an updated version of your documentation. I have streamlined the explanation, clearly documented the behavior of the slugifyGroupName function, and added a practical example so admins understand exactly how their labels turn into permission slugs.

Finding Group Names

Group names (slugs) are automatically generated from their associated display labels upon creation. Because permissions are tied directly to these generated names, updating a group's label after creation will break any existing permission implementations!

Conversion Reference

To find a group's name, apply the logic above to your label. Here are a few common examples of how labels translate to permission slugs in the webpanel: