TeamPanel

Message Content Intent

Evidence and explanation why TeamPanel needs Discord’s Message Content Intent (logging & ticket transcripts).

Message Content Intent

This page documents TeamPanel’s use case for Discord’s privileged Message Content Intent. It is a public evidence page for the Discord Developer Portal intent application.

Summary

TeamPanel only reads message content when server admins actively use Logging or Tickets — not for server-wide chat scraping and not for AI training.

Connected Discord bot

The bot is linked to the team’s Discord server (status in the TeamPanel dashboard):

Why we need the intent

1. Audit logging (message deleted / edited)

Admins configure a log channel and per-event toggles under Discord Bot → ModerationLogging. For deleted or edited messages the bot posts an embed with a short content excerpt (edits: before/after).

Without Message Content Intent Discord returns empty content fields, so moderation logging cannot work.

2. Ticket transcripts

When a ticket is closed (or “save transcript”), the bot builds an HTML transcript of messages in the private ticket channel. Staff can review that transcript later in TeamPanel.

What we do not do

  • no scraping of public channel history
  • no training of ML/AI models on message content
  • no advertising / tracking across the whole server chat

Storage & security

DataStoragePurpose
Log excerptsprimarily as Discord embeds in the configured log channelmoderation / audit
Ticket transcripts (HTML)TeamPanel API / team databasesupport follow-up

Discord’s Developer Terms require commercially reasonable security including encryption of API data at rest. TeamPanel stores ticket transcripts in the team database on infrastructure with disk / managed-DB encryption at rest, plus TLS in transit. Staff access is restricted to authorized team members.

Product: https://team-panel.dev

On this page