Getting started · Discord

# Connect your community’s Discord identity

For a Discord rollout, give learners and members a recognizable support entry point under your organization’s own identity.

## Start with the community and outcome

Choose the academy, trading-education program, startup ecosystem, or customer community the bot will support. Define the first request to resolve, such as finding a resource or restoring eligible access.

## Keep the application under your control

Use a Discord application owned by your organization and a name members recognize. Follow the Discord setup guide for application creation and connection. Store its token only through the designated secure configuration flow.

## Prepare knowledge before opening support

Collect current onboarding steps, program rules, resource locations, and the escalation owner. The bot’s identity does not automatically connect it to enrollment, subscription, or account records.

## Test with a representative member request

Check that the member can find support, receive a grounded answer, and reach the right person when needed. Verify any connected action separately before offering it to the community.

Illustrative support workflow

### “I have joined the academy. Where should I begin?”

Use the academy’s approved welcome guide to point the member to the first step and the relevant resources. Confirm access separately when the answer depends on a private enrollment.