1. Overview
The Discord integration reads one authorized server through an installed bot, preserving server, channel, thread, role, member, and message relationships.
Discord bot permissions and privileged intents define API reach, but they do not provide Seedling a complete human audience model for every channel and thread.
2. Connection and scope
Seedling verifies the provider account before storing the workspace connection. A current Seedling workspace administrator controls installation and disconnect; account identity is never inferred from an email address or display name.
- Discord bot token
- Create a Discord application and bot, install it into the intended server, and provide its token plus the stable server ID when available.
- Connection ownership
- This connector is workspace-only. A current Seedling workspace administrator controls installation, credential replacement, disconnect, and purge for the exact connection.
3. Discord data Seedling accesses
Seedling uses synchronized information for source-backed search, operating context, verification, and customer-approved workflows. Availability depends on the connected account, selected resources, provider plan, and native permissions.
- Server structure
- Server identity, channels, threads, roles, members, and permission-overwrite context.
- Messages
- Authorized message bodies, authors, timestamps, replies, reactions, embeds, and attachment metadata.
- Relationships
- Channel, thread, member, role, reply, reaction, and server relationships returned to the bot.
4. Read-only permission contract
Install the bot with the minimum gateway intents and server permissions required by the released reader.
- OAuth2 scope bot — install the application bot into the intended server.
- View Channels and Read Message History — enumerate visible channels and read available history.
- Message Content Intent — read message bodies; Server Members Intent — stage member-role mappings.
- View Audit Log is optional and is not required for ordinary message ingestion.
- No Send Messages, Manage Messages, Manage Channels, Manage Roles, or other server mutation permission is required.
5. Security and access
- Provider credentials and other connection secrets are encrypted in the workspace tenant data plane, never returned to the browser, and excluded from logs and queue payloads.
- Every source, synchronization, secret lookup, audience contribution, disconnect, and purge remains bound to the exact connection that created it.
- The provider does not expose enough complete object-level audience evidence for Seedling to reproduce native permissions safely. Workspace content therefore uses the connection's restricted-by-default workspace-or-no-human-access policy; administrator and steward status grant no raw-content bypass.
- Large or verified Discord apps may require provider review for privileged intents. Seedling does not claim complete message coverage until the required intents and server visibility are confirmed.
- Generated output cannot bypass Seedling's human review, verification, and approval gates.
6. Retention and deletion
- Connected data
- Synchronized Discord records remain while the connection is active and are removed through a durable integration purge after disconnect.
- Credentials
- Stored Discord credentials or connection secrets and connection-owned synchronization state are deleted from active Seedling systems as part of the purge.
- Backups
- Deleted information may remain in encrypted, access-restricted backups until expiry, ordinarily within 35 days after active-system deletion.