> ## Documentation Index
> Fetch the complete documentation index at: https://docs.headlesslabs.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# User tools

> Inspect profiles and histories observed by Headless, and understand each user command's scope and permissions.

This guide covers profile cards, observed name/avatar histories, and the commands that delete those records. Profile and name/avatar-history lookups do not require moderation permissions; `.userhistory` is a separate staff-only command. Deleting another person's data does require a permission check.

> **Before moderating**
>
> Review join date, primary roles, and whether the account appears new before deciding how to handle a case.

> **Visual profile data**
>
> Avatar, banner, and `serverinfo` help identify the profile and server. A banner appears only when Discord exposes one.

> **Privacy**
>
> These commands show public profile data or events observed by Headless. They do not expose tokens or internal data.

## Profile cards

* **`.userinfo [user]` · `/userinfo [member]` (`.ui`, `.whois`, `.uid`)** — **What it shows:** A Discord profile card with ID, available badges, creation/join dates, boost information, visible profile signals, and avatar/banner links. · **Scope:** Server only; omitting the member checks the caller.
* **`.avatar [user]` · `/avatar [member]` (`.av`, `.pfp`)** — **What it shows:** The current avatar and, for the prefix command, PNG and WebP links. · **Scope:** No elevated permissions. Prefix is server-only; if a prefix query does not resolve one unique member, the callback uses the caller.
* **`.banner [user]` · `/banner [member]` (`.bn`, `.userbanner`)** — **What it shows:** The profile banner; if there is none, it shows the accent color when Discord provides one. · **Scope:** Prefix is server-only and returns an error if the query cannot be resolved or is ambiguous.
* **`.serverinfo` · `/serverinfo` (`.si`, `.server`)** — **What it shows:** An information card for the current server. · **Scope:** Server only; no moderation permission required.

`userinfo` fields depend on what Discord exposes for the account. The card does not query private endpoints or claim a verified Nitro tenure; it shows profile signals that can be verified when available.

## Observed history

* **`.names [user]` (`.namehistory`, `.nombres`, `.oldnames`, `.previousnames`, `.prevnames`) · `/buscar nombres [member]`** — **What it checks:** Stored name and nickname history, up to 12 recent entries. · **Scope and restrictions:** Data from the current server; the slash lookup requires a server context. It cannot recover changes from before Headless observed them.
* **`.avatars [user]` (`.avatarhistory`, `.avhistory`, `.avatares`) · `/buscar avatares [member]`** — **What it checks:** A paginated collage of avatar history. · **Scope and restrictions:** Global per-user history, queried from a server. Shows up to 9 images per page; only the person who opened the result can use its controls.
* **`.userhistory <user>` · `/userhistory [member]` (`.history`, `.uh`)** — **What it checks:** A moderation/activity timeline with controls to open cases, refresh, and copy the ID. · **Scope and restrictions:** Staff lookup: requires Manage Messages and the access checks described in [User history](/docs/en/community/user-history.md).

These records are partial: they depend on events Headless received and stored. Name history is server-scoped; avatar history is a global profile record. A user may have fewer entries if the bot did not observe their changes.

## Deletion and permissions

* **`.clearnames [user]` · `/clearnames [member]` (`.cnames`, `.nameclear`, `.limpiarnombres`, `.clearnamehistory`, `.delnames`)** — **Data it deletes:** Name history for the current server and related name events. · **Who can delete another person's data:** Server owner or Headless owner, or native Manage Server, Manage Messages, or Moderate Members permission.
* **`.clearhistory [user]` · `/clearhistory [member]` (`.clearall`, `.limpiarhistorial`)** — **Data it deletes:** Name history for the current server and avatars in global history. · **Who can delete another person's data:** The same staff check.
* **`.avatarcache [user]` · `/avc [member]` (`.avc`, `.avatarclear`, `.clearavatars`, `.limpiaravatar`, `.limpiaravatars`)** — **Data it deletes:** Global avatar history and associated cached image references. · **Who can delete another person's data:** The same staff check. The prefix alias `.avc` also invokes `.avatarcache`.

`.clearnames`, `.avatarcache`, and `.clearhistory` delete data immediately without a confirmation prompt. You can clear your own history without a staff permission; to clear another person's data, the runtime accepts the Headless owner or any one of the listed native permissions. The command must be invoked in a server, and the bot attempts to record each action in that server's Logs.

> [!WARNING]
>
> `clearhistory` also removes global avatar history; it is not limited to the server where you run it. Check the target carefully. `clearnames` and `avatarcache` have different scopes: one clears local names, the other global avatars.

## Steps

**1. Inspect before deleting**

Use `userinfo`, `avatar`, `banner`, `names`, or `avatars` to identify the profile and history type.

**2. Check the scope**

`names` and `clearnames` are server-local; `avatars`, `avatarcache`, and the avatar portion of `clearhistory` are global.

**3. Choose the right deletion command**

Use `clearnames` for names, `avatarcache` for avatars, or `clearhistory` for both. Deletion is immediate and can affect data visible from other servers.

## Examples by workflow

### Profile information

#### `.userinfo`

```headless-command Syntax theme={null}
.userinfo [user_query]
```

```headless-command Example theme={null}
.userinfo @Member
```

```headless-command Syntax theme={null}
/userinfo [member:<member>]
```

```headless-command Example theme={null}
/userinfo member:@Member
```

#### `.avatar`

```headless-command Syntax theme={null}
.avatar [user_query]
```

```headless-command Example theme={null}
.avatar @Member
```

#### `.banner`

```headless-command Syntax theme={null}
.banner [user_query]
```

```headless-command Example theme={null}
.banner @Member
```

#### `.serverinfo`

```headless-command Syntax theme={null}
.serverinfo
```

```headless-command Example theme={null}
.serverinfo
```

### Observed names and avatars

#### `.names`

```headless-command Syntax theme={null}
.names [user_query]
```

```headless-command Example theme={null}
.names @Member
```

#### `/buscar nombres`

```headless-command Syntax theme={null}
/buscar nombres [user:<user>]
```

```headless-command Example theme={null}
/buscar nombres user:@Member
```

#### `.avatars`

```headless-command Syntax theme={null}
.avatars [user_query]
```

```headless-command Example theme={null}
.avatars @Member
```

#### `/buscar avatares`

```headless-command Syntax theme={null}
/buscar avatares [user:<user>]
```

```headless-command Example theme={null}
/buscar avatares user:@Member
```

#### `.userhistory`

```headless-command Syntax theme={null}
.userhistory [user]
```

```headless-command Example theme={null}
.userhistory @Member
```

### Delete history and cached data

#### `.clearnames`

```headless-command Syntax theme={null}
.clearnames [user_query]
```

```headless-command Example theme={null}
.clearnames @Member
```

#### `.clearhistory`

```headless-command Syntax theme={null}
.clearhistory [user_query]
```

```headless-command Example theme={null}
.clearhistory @Member
```

```headless-command Syntax theme={null}
/clearhistory [user:<user>]
```

```headless-command Example theme={null}
/clearhistory user:@Member
```

#### `.avatarcache`

```headless-command Syntax theme={null}
.avatarcache [user_query]
```

```headless-command Example theme={null}
.avatarcache @Member
```

#### `/avc`

```headless-command Syntax theme={null}
/avc [user:<user>]
```

```headless-command Example theme={null}
/avc user:@Member
```

## Related pages

* [User history](/docs/en/community/user-history.md)
* [Social and public lookups](/docs/en/community/social.md)
* [Moderation cases](/docs/en/moderation/cases.md)
* [Logging](/docs/en/server/logging.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.