
- ESX
- QBCore
- vRP
By Luke

Run a FiveM Discord ticket system with private tickets, limited staff permissions, restricted audit logs and a written retention rule.
Create separate roles for ticket users, support staff and ticket administrators. Let support staff read and reply only in assigned tickets; reserve role management, channel administration and bot configuration for a very small administrator group. Do not grant blanket Administrator permission to a ticket bot or every member of staff.
For a private channel, remove View Channel from @everyone and add only the requester, the assigned support role and administrators who need escalation access. For a private thread, invite the requester and assigned staff individually; members with Manage Threads can view all private threads. Avoid copying payment or account credentials into the ticket, and verify access with a test account before opening the system.
Keep an auditable staff log for ticket creation, assignment, permission changes, closure and escalation. Restrict log access to people who need it. If you export transcripts, treat them as support records: do not post them publicly, do not send them to unrelated integrations, and remove sensitive data before sharing an excerpt.
Write down how long open tickets, closed tickets, transcripts and staff logs are retained, who may access them, and how deletion is performed. At closure, stop replies, review participant and staff access against that rule, then delete or archive the ticket through the documented authorized process. Test the closed state with an unprivileged account.
Review role assignments, channel permissions, integration scopes and retention at regular intervals and after any staff or bot change. Choose a maintained ticket tool only after checking its permissions, data handling and current documentation.





