A complete list of all available permissions and how to use them.
Z-UCP uses a fine-grained permission system. Every administrative action is protected by a specific permission.
Permissions are usually structured hierarchically: module.action or module.submodule.action.
Here are the most important permissions, divided by modules:
player.*)player.view: Allows searching and viewing player profiles.player.ban: Allows banning players.player.kick: Allows kicking players via the bridge.player.note.create: Allows creating administrative notes on players.player.report.manage: Allows managing player reports.cms.*)cms.pages.view: Access to the CMS page overview.cms.pages.edit: Allows editing content on the landing page.cms.navigation.manage: Allows changing header and footer menus.cms.media.upload: Allows uploading media (logos, images).database.*)database.read: Allows access to the database browser.database.write: Allows changing rows and values.database.console: Allows access to the SQL console.database.backup.create: Allows manual creation of backups.system.*)system.settings.view: Access to project settings.system.settings.edit: Allows changing project name, domain, and whitelabeling.system.billing.view: Access to the billing overview and tier management.Every action protected by a permission is linked to the performing user in the Audit Log. There are no "anonymous" administrative actions.