# Direct Messages Design Guidelines

## Badge when online elsewhere

The badging logic in direct-messages is consistent with the logic detailed in the [Unified Friends List](/guides/friends-relationships-design-guidelines-unified-friends-list) section.

If the user is **online elsewhere** and is not in the game client, their usernames will include a **Discord badge**. Once they're online in the game-client, they will not retain the Discord badge.

![Badge when online elsewhere](../img/images/social-sdk/design-guidelines/animated/DMs-02.gif)

## Message styling

Style the Discord logo to match a player's username color. The logo should feel tied to a user's identity, not the message content.

![Message styling](../img/images/social-sdk/design-guidelines/DMs-03.png)

## Unsupported rich media

Regardless of whether a user has signed into Discord, unsupported rich media content should be paired with an **external link icon**.

When content isn't clickable, don't show the icon.

![Unsupported rich media](../img/images/social-sdk/design-guidelines/DMs-04.png)

***

## Resources

- [Development Guide: Direct Messages](/guides/direct-messages-development-guides-sending-direct-messages)

## Change Log

| Date           | Changes         |
| -------------- | --------------- |
| March 17, 2025 | initial release |

## Related pages

- [API Reference](./api-reference-index.md)
- [App Fundamentals](./app-fundamentals-index.md)
- [Best Practices](./best-practices-index.md)
- [Bots & Companion Apps](./bots-companion-apps-index.md)
- [Building Games](./building-games-index.md)
- [Building on Discord](./building-on-discord-index.md)
- [Change Log](./change-log-index.md)
- [Communities & Servers](./communities-servers-index.md)
- [Components](./components-index.md)
- [Core Concepts](./core-concepts-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.