> For the complete documentation index, see [llms.txt](https://mykolapetrovych.gitbook.io/argus-wordpress-plugin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mykolapetrovych.gitbook.io/argus-wordpress-plugin/version-6.1.0/general-functions/steam/manually-attaching-discord-profile.md).

# Manually Attaching Steam Profile

You can manually attach the Steam profile to the WordPress user by assigning a Steam ID.

If you go to your personal profile page in the WordPress admin panel and scroll down to see a ***Steam Data*** section, you will find connected Steam profile data and a button to re-connect a new one.

If, as the website administrator, you go to the same place on other user profiles, you will find an option to attach the Steam profile manually by saving the Steam user ID.

{% hint style="danger" %}
If you attach the wrong ID, another person can log in with this WordPress account. Also, a new account will be created when the correct person returns.
{% endhint %}

[Here](/argus-wordpress-plugin/version-6.1.0/general-functions/steam/how-to-find-discord-ids.md), you'll be able to read more about finding the Steam user ID.


---

# 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://mykolapetrovych.gitbook.io/argus-wordpress-plugin/version-6.1.0/general-functions/steam/manually-attaching-discord-profile.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.