SYS.HOME/CHROMATICKETS/SETUP

SYS.SETUP

> CHROMA TICKETS — Installation & Configuration Guide

Follow these steps to get Chroma Tickets fully operational in your Discord server. Most configuration happens in the web portal — the bot handles the rest.

← OverviewCommand Reference →
01

Invite Chroma Tickets to Your Server

Use the official invite link to add the bot to your Discord server. Chroma Tickets requires the following permissions to operate correctly:

  • Manage Channels (required to create, move, rename, and delete ticket channels)
  • Manage Roles (required to set per-ticket channel permissions)
  • Send Messages & Embed Links (required for panels, ticket embeds, and responses)
  • Attach Files (required to post HTML transcripts)
  • View Channels (required to operate in channels)
  • Read Message History (required to generate transcripts)

> IMPORTANT

The bot creates and manages ticket channels inside your configured categories. Make sure its role has access to those categories in Server Settings → Roles.

Add to Guild
02

Activate Your Subscription

Chroma Tickets requires an active guild subscription. Licensing is handled entirely through the ChromaLabs web portal:

  1. Sign in to the ChromaLabs Portal with Discord
  2. Open Chroma Tickets and select your server
  3. Go to Subscription and choose a plan

Plans

Monthly $4.99 · Quarterly $14.97 · Semiannual $29.19 · Yearly $49.00

NOTE

Without an active subscription the bot will refuse to open tickets and point members to chromalabs.dev.

03

Configure Tickets in the Web Portal

Unlike traditional ticket bots, Chroma Tickets is configured almost entirely from the web portal — no config commands to memorize. Open your server in the portal and work through:

> Subjects — ticket types, questions & opening embeds
> Panels — panel embeds and their buttons
> Categories — where tickets open, overflow & transcripts
> Server Settings — defaults and limits
> Integrations — external API checks
> Move Rules — category-to-category workflows
> Permissions — staff trigger grants
> Manager Roles — who can edit portal config

At minimum, create one category (with a transcript channel) and one subject (ticket type). Add up to 5 modal questions per subject — answers can be validated with regex and rendered into the ticket's opening embed with {answers.x} variables.

04

Publish Your First Panel

Once a panel is built in the portal, publish it into the channel where members should open tickets:

/dynamictickets publishpanel <panel_key>

Run this in the channel where the panel should appear (admin only)

Members click a panel button — or run /ticket open — answer the questions, and their ticket channel is created in the configured category automatically.

> TIP

Edit the panel in the portal at any time — republish to update the message in Discord.

05

Grant Staff Permissions

Chroma Tickets uses the ChromaLabs trigger-based permission engine. By default only the server owner and Discord administrators have full access — grant your support team the triggers they need:

/set permission <Add|Remove> <trigger> [role] [member]

Example: Let your support role claim tickets

/set permission Add [claim_ticket] [@Support]

Available triggers:

> claim_ticket
> delete_ticket
> move_ticket
> force_transcript
> claim_leaderboard
> active_claimed
> guild_admin

Audit grants at any time with /list_permissions, or manage them from the portal's Permissions tab.

> SETUP_COMPLETE

Bot is configured — now what?

Browse the full command reference to explore every available command, its parameters, and required permissions.

View Command Reference