# Per-panel log overrides

Each panel can override the **opened** and **closed** log channels independently of the server-wide defaults. Useful when different ticket types should be logged to different places.

## How to configure

In the panel editor, open the panel-wide defaults editor. Two fields control the per-panel log channels:

* **Default Ticket Open Log Channel**
* **Default Ticket Close Log Channel**

Each field can be left to use the server-wide channel, or set to a value of your own. When you set one, the value can be:

* A **channel** (where this panel's logs go instead).
* **No channel** (this panel's open or close events are not logged at all).

Sending a panel's logs to a different channel is the common case. Setting it to no channel is useful when you have a high-volume panel whose logs you do not need.

<figure><img src="/files/xMzWienbT8g6gguSYUYW" alt="The panel-wide defaults editor showing the Default Ticket Open Log Channel and Default Ticket Close Log Channel fields,"><figcaption></figcaption></figure>

## How the bot picks the channel

When a ticket opens or closes, the bot decides where to log it:

1. **If the panel sets its own log channel,** the bot uses that channel, or skips logging if the panel is set to no channel.
2. **Otherwise,** the bot falls back to the server-wide Opened Tickets Log Channel or Closed Tickets Log Channel.

## Application panels

Application panels have their own **Log Channel** field on each option, and it is required. This is not the same as the ticket log channels.

→ [Designing your application](/docs/applications/designing-your-application.md)

## Worked example

Server has:

* Opened-tickets log: `#tk-opened-tickets`.
* Closed-tickets log: `#tk-closed-tickets`.

Panels:

| Panel           | Open log                     | Close log                    |
| --------------- | ---------------------------- | ---------------------------- |
| General Support | (inherit)                    | (inherit)                    |
| Bug Reports     | Override → `#bug-tracker`    | Override → `#bug-tracker`    |
| Staff Tickets   | Override → `#staff-internal` | Override → `#staff-internal` |

Result:

* General Support tickets open/close logs go to the default channels.
* Bug Reports tickets log to `#bug-tracker` exclusively.
* Staff Tickets log to `#staff-internal` (kept separate from member-facing logs).

## Related

{% content-ref url="/pages/BdzAJh6nhAgNyRVnzgM9" %}
[Log channels](/docs/logging/three-log-channels.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ticketking.xyz/docs/logging/per-panel-overrides.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.