# Discord

Receive personal approval notifications through your connected Discord server.

Discord notifications arrive as direct messages from withHuman. Your organization connects a server through the [Discord integration](/docs/web-app/discord-integration), and you link your own Discord account to receive messages.

## Account linking

Your Discord account must belong to the connected server. Linking uses Discord sign-in and does not depend on matching your withHuman email address.

The Channels list shows **Linked** when the account is ready. Discord must allow direct messages from members of that server, otherwise the withHuman bot cannot reach you.

If no server is connected, someone who manages integrations needs to connect it first. The personal link belongs to this organization.

## Rules and messages

The default **Interrupts** rules use Discord immediately when Slack is not linked, followed by account email after five minutes. **Standard requests** use email by default. Your saved [notification rules](/docs/web-app/notifications#standard-requests-and-interrupts) can choose Discord for either urgency.

Messages show the tool, agent and expiry, with **Open in withHuman** linking to the request. Request arguments stay in withHuman. Review and decide there; Discord replies do not record a decision.

Escalation paths reach you through these personal DMs when your notification rules select Discord.

## Delivery and unlinking

If messages are missing, check your server membership, Discord's DM privacy settings and your saved notification rules. Being linked does not override Discord's restrictions on messages.

Unlinking removes your personal Discord channel and its rules. Disconnecting the organization's server removes every member's link. Keep another channel available, and see [Delays](/docs/web-app/notifications#delays) for timing and claims.