KNOWLEDGE FOR TEAMS

Implement with clear ownership

Use the technical tutorials as a controlled implementation path for administrators, moderators and support teams.

Book a consultation →View Trust Center
HubNova›Implementation centre›Tickets
Safety & AutomationPro plan

Tickets

A controlled implementation runbook for Tickets, suitable for teams and multiple servers.

◷ 10 MIN READ✓ 5 stepsReviewed: 26 September 2026
START GUIDE ↓
01
THE MODULE

What does Tickets?

Implement Tickets with clear ownership, least privilege, test evidence, and verified handover.. This guide covers readiness, configuration, validation, launch, and ongoing ownership.

SERVER-SPECIFIEKPlan, settings, permissions, and AI Credits always belong to the selected server.
02
OUTCOMES

What you will achieve

01

Tickets is configured for the selected server

02

Channels, roles, and exceptions are deliberately scoped

03

The setup is tested and has a clear owner

03
READINESS

Before you start

✓An assigned process owner and technical administrator
✓An approved test server or restricted test channel
✓An active Pro or Elite package within the approved scope
04
LEAST PRIVILEGE

Access & permissions

⌁

Dashboard access to the selected server workspace

⌁

Only the Discord permissions and channels required by this module

05
PLAYBOOK

Tickets setup

Complete the steps in order. Your progress is stored only in this browser.

STEP 1

Verify server and readiness

Select the correct server, open Tickets, and resolve every blocking setup check.

STEP 2

Configure the essentials

Choose the behaviour, limits, channels, roles, and exceptions that fit your community.

STEP 3

Apply least privilege

Grant only the required access and make sure HubNova can reach every configured resource.

STEP 4

Preview and test safely

Use a restricted channel or test role and verify the member and administrator experience.

STEP 5

Launch and review

Enable the module, inspect the first live results, and schedule a periodic configuration review.

06
DISCORD

Available Discord commands

Availability depends on the server plan, module settings, and your Discord permissions.

/ticketUse /ticket in Discord for the related server-scoped action.
/claimUse /claim in Discord for the related server-scoped action.
/transferUse /transfer in Discord for the related server-scoped action.
/ticket-statusUse /ticket-status in Discord for the related server-scoped action.
/tagUse /tag in Discord for the related server-scoped action.
/unclaimedUse /unclaimed in Discord for the related server-scoped action.
/staff-statsUse /staff-stats in Discord for the related server-scoped action.
/closeUse /close in Discord for the related server-scoped action.
07
SUPPORT

Troubleshooting

01The module is disabled again after refresh+

Check required fields, plan access, and blocking Setup Health findings before enabling it again.

02A channel or role is missing+

Refresh Discord resources and verify the bot role, selected server, and channel access.

03The test works but members see nothing+

Review channel overrides, member roles, visibility, and test-only targeting.

08
BEST PRACTICES

Best practices

  • Verify the selected server before every change.
  • Start in a restricted test channel or with a test role.
  • Assign a module owner and periodically review access, exceptions, and results.
  • Use /help or /commands for the current server-specific command list.
09
NEXT UP

Continue learning

RELATED GUIDEAccess Passes→RELATED GUIDEBot Branding Studio→RELATED GUIDEComponents Studio→
Pro · Safety & Automation

Ready to implement: Tickets?

Open the correct organisation workspace, assign an owner, and complete the runbook.

OPEN WORKSPACE →