> ## Documentation Index
> Fetch the complete documentation index at: https://docs.razebot.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Options

> Topics define the individual ticket types shown on the panel dropdown.

# Options

> Topics define the individual ticket types shown on the panel dropdown.

Each topic is an independent ticket type with its own category, permissions, claim behaviour, channel naming, and optional form. Topics appear as dropdown options when a member interacts with the panel.

<Frame caption="A topic dropdown on a live ticket panel.">
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/raze/images/topic-dropdown.png" alt="Ticket topic dropdown" />
</Frame>

Requires <Tooltip tip="Users with Administrator permission or added as a ticket admin via ;ticket admin add.">Administrator</Tooltip> to configure topics.

***

## Behavior

Controls how tickets in this topic act and who can act on them.

### Claim effect

When a staff member claims a ticket, the topic's claim effect determines what happens to the channel.

```bash theme={null} theme={null}
;ticket topic claimeffect (topic) (none|hide|rename)
```

| Value    | Effect                                                  |
| -------- | ------------------------------------------------------- |
| `none`   | No change — all support staff can still see the channel |
| `hide`   | Removes channel access for all other support staff      |
| `rename` | Renames the channel to `claimed-{username}`             |

### Permissions

Set who can close or delete tickets in this topic.

```bash theme={null} theme={null}
;ticket topic permissions (topic) (close) (delete)
```

| Value      | Who can act                               |
| ---------- | ----------------------------------------- |
| `support`  | Support staff and ticket admins (default) |
| `everyone` | The ticket owner and support staff        |
| `admin`    | Ticket admins only                        |

**Example:**

```bash theme={null} theme={null}
;ticket topic permissions support everyone admin
```

This lets anyone close tickets in the `support` topic, but only admins can delete them.

### Form answers

Toggle whether the submitted form responses are posted inside the ticket channel when it opens.

```bash theme={null} theme={null}
;ticket topic formanswers (topic)
```

Enabled by default. Disabling this keeps form data server-side only.

***

## Categories

Where tickets from this topic open and close.

### Open category

```bash theme={null} theme={null}
;ticket settings category (topic) (category)
```

Overrides the global default category for this topic specifically.

### Closed category

```bash theme={null} theme={null}
;ticket topic closed (topic) (category)
```

When a ticket in this topic is closed, the channel moves here. Falls back to the global closed category if not set.

**Category priority order:**

1. Topic's own category *(most specific)*
2. Panel's category override
3. Global default category *(fallback)*

***

## Naming

How the ticket channel is named and described.

### Channel name pattern

```bash theme={null} theme={null}
;ticket topic channelname (topic) (pattern)
```

<ParamField path="pattern" type="string">
  Template string for the channel name.

  <Expandable title="variables">
    <ResponseField name="{user}" type="string">Display name of the ticket opener.</ResponseField>
    <ResponseField name="{username}" type="string">Username of the ticket opener.</ResponseField>
    <ResponseField name="{number}" type="number">Auto-incremented ticket count.</ResponseField>
    <ResponseField name="{topic}" type="string">The topic name (slugified).</ResponseField>
  </Expandable>
</ParamField>

**Example:**

```bash theme={null} theme={null}
;ticket topic channelname support ticket-{username}-{number}
```

### Channel topic

```bash theme={null} theme={null}
;ticket topic channeltopic (topic) (text)
```

Sets the Discord channel topic/description shown at the top of the ticket channel.

```bash theme={null} theme={null}
;ticket topic channeltopic support Support ticket for {user} · opened {ticket.opened_at}
```

<Tip>
  Channel topic text supports the same pattern variables as the channel name, plus [ticket variables](/server-config/tickets/variables).
</Tip>

***

## Style

How the topic appears in the panel dropdown and in listings.

### Name, emoji, description

```bash theme={null} theme={null}
;ticket topic name (old) (new)
;ticket topic emoji (topic) (emoji)
;ticket topic description (topic) (text)
```

The description appears as hint text under the topic name in the dropdown.

### Status

```bash theme={null} theme={null}
;ticket topic status (topic) (open|closed)
```

Closing a topic hides it from members without deleting its configuration. Useful for temporarily disabling a topic.

### Sort weight

```bash theme={null} theme={null}
;ticket topic weight (topic) (number)
```

Higher weight = shown higher in the dropdown. Default is 0.

### Opening embed

```bash theme={null} theme={null}
;ticket settings embed (topic) (embed code)
```

Sent inside the ticket channel immediately after it opens. Supports [embed scripting](/resources/scripting/embeds) and [ticket variables](/server-config/tickets/variables).

**Example:**

```bash theme={null} theme={null}
;ticket settings embed support {embed}$v{color: #7B68EE}$v{title: 👋 Welcome}$v{description: Hey {ticket.creator.mention}, a staff member will be with you shortly.}
```

***

## Access

Per-topic role overrides on top of global access settings.

### Support roles

```bash theme={null} theme={null}
;ticket support add (topic) (@role)
;ticket support remove (topic) (@role)
;ticket support list
```

### Per-topic admin roles

Roles with full admin access scoped to this topic only.

```bash theme={null} theme={null}
;ticket topic admin add (topic) (@role)
;ticket topic admin remove (topic) (@role)
```