All guides

Connect Discord and import members

Understand the shared Harbor bot, white-label bots, import status, and message reading.

Reviewed Nov 13, 2026View .md

Connect through Harbor

During onboarding, choose Add Harbor to Discord, select a server you can administer, and authorize the bot. Finish the connection in the original dashboard browser session. A successful connection queues the existing-member import and opens the Discord CRM. Simply inviting the bot outside this flow does not complete Harbor’s verified project connection.

What gets imported

The shared Harbor bot imports Discord member profiles and roles. Subsequent membership and profile events keep the CRM current, with background reconciliation. Fans do not need to sign up for Harbor first. The import count can include bots, while the CRM member list excludes bots and departed members; these totals can differ.

Projects with a configured white-label bot retain that bot as their member and role source. Shared-bot import does not automatically enable every white-label bot action, including existing role-assignment paths.

When Discord analytics is on for the project, the shared Harbor bot also reads messages in the channels it can see, so conversations can be summarised and scored. See Sentiment, Steam reviews and discussions. Connecting through Harbor turns Discord analytics on when it has never been set. A project that turned it off stays off, and a server connected before message reading existed is not read until analytics is switched on.

When the import is not ready

Check the connection and import status before reconnecting. Confirm you selected the intended server and are still in the original project and browser session. If bot access was removed, restore access and retry the connection/import flow. A server already linked to another project, or a project already linked to another server, can require resolving that conflict first.

Use Settings → Integrations for connection configuration and Audience to inspect members. For application-level intent or OAuth errors, ask the Harbor operator to check the shared bot configuration; do not paste bot tokens into chat or support screenshots.