> 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/bot-commands/unlinksteam.md).

# /unlinksteam

## Unlink Steam Command

### Overview

The `/unlinksteam` command removes a linked Steam account. Members can unlink their own; staff can unlink someone else's. The link is per server, so unlinking here does not affect other servers using Ticket King.

### Usage

```
/unlinksteam [user]
```

* **user** *(optional)*: The member whose Steam account to unlink. Staff only. Leave it out to unlink your own.

The reply is private either way.

### Description

* **Without the option**, you unlink your own Steam account for this server.
* **With the option**, staff unlink that member's Steam account for this server.
* **It is not a ban.** The member can link again at any time by going through the normal Steam Linking flow.
* **Unlinking has no effect on existing tickets.** A `{STEAM_ID}` already substituted into a channel name stays as it is.

### When to Use It

* A member linked the wrong Steam account.
* An account changed hands, or a member is switching to a different Steam profile.
* Staff need to clear a stale or incorrect link during a support ticket.
* A member asks for their Steam link to be removed from your server.

### Permissions

* **Unlinking your own** needs no permissions.
* **Unlinking another member's** requires Manage Channels or Manage Server, or being the server owner, or holding an authorized support role. Administrator also works because it includes those permissions. Without one of these, the bot refuses.

### Notes

* Steam Linking itself is a Premium feature, and options can require a linked account before a ticket opens. Unlinking a member from an option that requires Steam means they will be asked to link again next time they use it.

### Example

```
/unlinksteam
```

Unlinks your own Steam account for this server.

```
/unlinksteam user: @Member
```

Staff unlinks that member's Steam account for this server.

### Related

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

{% content-ref url="/pages/PkofzTunLSivCzcDejtr" %}
[What members see](https://ticketking.xyz/docs/steam-linking/what-members-see.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/bot-commands/unlinksteam.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.
