v3.3.2

Fixed

Admins with group.admin could not open the dashboard. FiveM keeps principals and ace objects apart. A line like add_principal identifier.license:xxx group.admin in your server.cfg only makes that player a member of the group, it does not give them the ace object of the same name. The dashboard checked for exactly that ace object, so unless someone had also written add_ace group.admin group.admin allow by hand, the check came back empty and the player was turned away. It worked on some servers by accident, because there the ESX or QBCore group in the users table happened to be admin as well and the framework fallback caught it. The script now creates those ace objects itself on start, for admin, for every group in Config.dashboardGroups and for every group in the permission matrix. A plain add_principal in your server.cfg is enough now. Groups you add from the Permissions tab are covered right away, no restart needed.
Checking a group name in the Permissions tab reported "not found" for brand new groups. The check ran before the group existed as an ace object, so it could never find anyone in it. The group is registered first now.

There is nothing to rebuild and no database change. Replace the resource files and restart it.

Cannot update right now?

This one line in your server.cfg has the same effect for group.admin:

add_ace group.admin group.admin allow

Debugging access problems

With Config.Debug = true the server now prints why a player was denied and what each check answered (ace permission and framework group, per group).

Changed files

fxmanifest.lua
server/admin/permissions.lua
server/admin/boot.lua
server/admin/api.lua
server/admin/command.lua
config/settings.lua

Changed files​

Changed files