If you message Dawn from a Telegram DM and later sign in to Dawn Web, those should feel like the same experience. Before this release, they often did not. Dawn treated each channel as a separate surface with its own identity, so the same person could appear anonymous the moment they switched tools.
This release fixes that with identity linking.
How to Link Your Identity
The flow starts from a private channel conversation. In a Slack DM, Telegram private chat, Teams personal message, or Discord DM with the Dawn bot, type /link followed by your email address:
/link [email protected]Dawn sends a verification email to that address. The email contains a short display code and a confirmation link. Open the link, sign in to your Dawn account if needed, and enter the display code to confirm. The link takes about a minute to complete.
Once confirmed, Dawn permanently connects that channel identity to your Dawn account. You only need to do this once per channel. You can check whether your identity is linked at any time by typing /link status in a private channel conversation. See slash commands in Dawn for more on command discovery.
What Changes After Linking
Consistent recognition. Before linking, Dawn treats a Telegram user and a Dawn Web user as separate people even if they are the same person. After linking, Dawn knows they are the same account. Your name, access, and context carry across surfaces.
Workspace access follows you. If you are a teammate in a workspace through Dawn Web, that same access applies when you message Dawn from a linked channel. You do not have to be separately recognised in each place. In workspaces that have auto-join enabled, a confirmed link can also grant you teammate access automatically.
Cleaner private conversations. Private channel conversations from a linked identity are associated with your real Dawn account. That means the experience is more personal and less anonymous — the agent knows who you are and can apply the right workspace context.
The Verification Step Matters
Dawn does not assume that a Slack or Telegram user is the same as a Dawn Web user just because something looks similar. The linking flow requires explicit verification — you provide your email, receive a code, and confirm from your signed-in Dawn account. The code is valid for 60 minutes and can only be used once.
That is intentional. Identity claims from external channels should not be trusted without the user actively confirming the connection. This protects against someone impersonating a teammate from an external channel.
Where This Helps Most
Teams that use Dawn from multiple places benefit the most. If your team uses Slack for quick questions during the day and Dawn Web for longer research sessions, linking means Dawn recognizes you in both places without you having to prove who you are every time you switch.
It is also useful for workspace owners. When Dawn can confidently identify a user across channels, access decisions become simpler. The product does not have to guess whether the person in a private Telegram chat is the same person who signed up through Dawn Web — it knows, because the link was verified.
What This Does Not Do
Linking connects identities, but it does not merge conversation history. Your Slack threads and your Dawn Web threads stay separate. What changes is that Dawn recognizes the person behind them as the same account.
Linking is also per-channel, not automatic across all channels. If you use both Slack and Telegram, you link each one separately. Each channel identity is verified independently.
Getting Started
From any private conversation with the Dawn bot on Slack, Telegram, Teams, or Discord, type /link [email protected]. Check your email for the verification code, confirm it in Dawn Web, and you are done. Type /link status anytime to check your linked status.