Discord

The Discord integration connects a server to your organization and adds the withHuman bot. Members then link their own accounts so the bot can send them personal approval notifications.

Integrations manages the shared server connection. Discord notifications covers each person's link and notification preferences.

Server connection

Connecting requires permission to manage integrations in withHuman and authorization to add the bot to the Discord server. The authorization happens in Discord, where an administrator chooses the server.

The bot uses direct messages and does not request server permissions for posting in channels. An organization can connect one server. A server already connected to another organization cannot be claimed by a second one.

Connected shows the server name, its identifier and when it was connected. Not enabled means Discord needs to be configured on the deployment first. If authorization is declined or expires, a new connection attempt is needed.

Linked members

Each person links their account through Discord sign-in under Notifications. The account must be a member of the connected server. Discord has no email-based member sync, so installing the bot alone does not link everyone.

Linked members counts active withHuman members with a Discord link. Linking does not invite anyone to the server, grant review permissions or change escalation paths. One Discord account cannot be linked to two members in the same organization.

Members must allow direct messages from the connected server. A linked account can still miss messages if Discord's privacy settings block the bot.

Example: A Payments reviewer joins Discord

We'll connect the server our Payments reviewers already use. Each reviewer links their own Discord account and chooses Discord in their notification rules. A new reviewer needs to belong to that server before their account can be linked.

Notification rules

Personal rules choose when Discord receives a request. Connecting the server does not add Discord to rules members have already customized.

Approval notifications arrive as DMs with a review link. Members open the request in withHuman to approve or deny it. Replies and posts in Discord channels do not record decisions.

Disconnection

Disconnect removes the organization's server connection and every member's Discord link. Rules using those links are removed too, and withHuman asks the bot to leave the server.

Members' other notification channels remain available. If removing Discord leaves an urgency with no saved rules, the default notification rules apply again.

Connecting a server later requires members to link their accounts again. Members who use customized rules need to add Discord back where they want it.

An individual can unlink Discord under Notifications without disconnecting the organization. Connection changes remain in Audit log; the Integrations overview covers management access.