> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/steam-linking/requiring-on-a-panel-option.md).

# Requiring Steam linking on a panel option

Make members link Steam before a specific panel option opens.

<i class="fa-crown">:crown:</i> **Premium feature.** To make members link their Steam account before they can open a specific panel option:

## The per-option toggle

In the panel editor, open the option, go to the **Advanced tab**, find the **Steam ID Integration** section, and turn on the **Require Steam Linking** toggle.

When it is on, clicking this option starts the Steam link flow first, if the member is not already linked, before the ticket form opens.

## Inheritance

The toggle can either follow the panel default or be set for this option on its own:

* **Use the panel default.** The option follows the panel's Steam ID Integration setting.
* **Set it here.** The option uses its own on or off value.

The panel default is set under **Panel Defaults**, in **Default Steam ID Integration**.

<figure><img src="https://1268186137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrnuG1qjzbOoh0efVpoK8%2Fuploads%2Fgit-blob-aea9b17dda48cad4c186535422285339c01c079e%2Fsteam-id-integration-toggle.png?alt=media" alt="A panel option&#x27;s Advanced tab with the Steam ID Integration section and Require Steam Linking toggle"><figcaption></figcaption></figure>

## When to require it

* Game-specific options where account ownership matters, such as "Report a hacker", "Item dispute", or "Account help".
* Supporter or VIP options where the Steam ID helps confirm who is eligible.
* Refund or trade options where you need a Steam account on file.

## When not to require it

* General support, where adding a link step gets in the way of a member who only wants to ask a question.
* Application options. Use the application's eligibility rules instead, such as account age, server age, or a required role.

Steam ID Integration is a Premium feature.

## Combined with form questions

Steam linking is separate from form questions. A panel option can be set up in any of these ways:

* No questions and no Steam link.
* Form questions only.
* Steam link only.
* Both Steam link and form questions. The member links first, then fills in the form, then the ticket opens.

## If premium ends

If your server goes from premium back to free:

* Members who already linked keep their stored Steam ID.
* Clicking the option opens the ticket without the link step.
* When premium returns, the option requires linking again.

## Placeholders this enables

When Steam ID Integration is on and your server has premium, you can use the `{STEAM_ID}` placeholder in:

* The custom ticket name.
* The Custom Ticket Embed Message.
* The Custom Ticket Message.
* The Admin Thread Message.

## Related

{% content-ref url="/pages/xl8ZOlixZa4z69uy07g9" %}
[What Steam Linking does](https://ticketking.xyz/docs/steam-linking/overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/aHGH6BOJh48aZHUVoiWW" %}
[Per-option settings](https://ticketking.xyz/docs/panels/per-option-settings.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ticketking.xyz/docs/steam-linking/requiring-on-a-panel-option.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
