Quick Actions

Quick actions are handled in server callback gcm_reports:admin:quickAction.

Supported actions

• bring
• goto
• bringback
• back
• teleport
• inventory
• giveitems
• revive
• ropa
• bucket
• screenshot (quickAction reports success path; actual capture/upload is handled by modal callback)
• espectar

Permission checks

Most actions require member:hasPermission('<perm>') (unless staff has full access):

• teleport
• inventory
• giveitems
• revive
• ropa
• bucket
• spectate
• screenshot

Staff access hierarchy

Staff bootstrap now follows this order:

1. Config full access (Config.StaffFullAccess)
2. Panel-managed staff/group assignment (gcm_reports_staff.group_id)
3. Config basic access (Config.StaffBasicAccess)

This means a player with basic config access who is assigned to a panel group will use the panel group permissions.

Basic access behavior

When staff resolves through Config.StaffBasicAccess and has no panel group assignment:

• Quick actions remain available except giveitems.
• Item-give permission is intentionally blocked (giveitems = false), so item delivery must be granted via a dedicated panel group.

Side effects

• Most quick actions append a staff message to report chat.
• SavedCoords is used for bringback and back restore flows.
• bucket updates routing bucket with SetPlayerRoutingBucket.
• espectar triggers txcl:spectate:start on staff client.
• inventory, revive, and ropa now return backend failure when the detected integration is unsupported instead of always reporting success.
• Each quick action can emit a dedicated Discord log type through config/logs.lua webhooks (quick-* keys).

Backend support notes

Inventory quick action

• Native success path:
  • ox_inventory
• Custom adapter success path:
  • qb-inventory
  • ps-inventory
  • origen_inventory
  • core_inventory
  • tgiann-inventory
  • jpr-inventory
• Detected but not currently openable through gcm_reports:
  • qs-inventory
  • codem-inventory

Clothing quick action

• Supported:
  • esx_skin
  • qb-clothing
  • illenium-appearance
  • fivem-appearance
  • rcore_clothing
  • origen_clothing

Revive quick action

• Supported:
  • qb-ambulancejob
  • qbx_medical
  • wasabi_ambulance
  • esx_ambulancejob
• Fallback:
  • ESX uses esx_ambulancejob:revive
  • QBCore/QBX uses hospital:client:Revive

Screenshot flow (modal)

1. Staff calls gcm_reports:admin:takeScreenshotForModal.
2. Server validates screenshot permission + screenshot-upload webhook (config/logs.lua, with legacy fallback to Config.discordWebhook).
3. Server requests capture from target client (gcm_reports:client:takeScreenshot).
4. Client uploads with screenshot-basic and returns image URL.