# Profile & Account

{% hint style="info" %} <sub>If you skip profile hygiene, you still ship. You just ship with a name nobody recognizes in Leaderboard, and that is a tax on trust.</sub>
{% endhint %}

<h2 align="center"><sub>This page means</sub></h2>

<table><thead><tr><th width="309">This page is</th><th>This page is not</th></tr></thead><tbody><tr><td><sub>Orientation for founders and operators</sub></td><td><sub>A full identity provider spec (your IdP vendor owns that story)</sub></td></tr><tr><td><sub>What to fill in before you invite others</sub></td><td><sub>Legal advice about data residency</sub></td></tr></tbody></table>

<h2 align="center"><sub>What lives here</sub> </h2>

<sub>**Display name.**</sub> <sub></sub><sub>What humans see in the UI and in lightweight exports.</sub>

<sub>**Email and account linkage.**</sub> <sub></sub><sub>Whatever your deployment uses for sign in. If something looks wrong, fix it at the identity layer first, then return here.</sub>

<h2 align="center"><sub>ARIA Suggestion</sub></h2>

{% stepper %}
{% step %} <sub>**Set the display name before your first demo**</sub>

<sub>It is a 10s win that prevents “NA” energy in screenshots.</sub>
{% endstep %}

{% step %} <sub>**Match your wallet label to your username when you can**</sub>

<sub>It reduces confusion</sub>
{% endstep %}

{% step %} <sub>**Revisit after a rebrand if needed**</sub>

<sub>If the operator name changes, update your profile before you export anything customer facing.</sub>
{% endstep %}
{% endstepper %}

<h2 align="center"><sub>Ask a question</sub></h2>

<p align="center"><sub><strong>Would a stranger looking at your profile trust that this workspace belongs to a real operator?</strong></sub><br><sub>If not, fix the display name and avatar before you chase API keys.</sub></p>


---

# 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://docs.ariaagi.com/settings-and-integrations/profile-and-account.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.