Until now, everyone who used Dawn through the browser had to be an owner or a manager. That was fine when Dawn was an operator tool, but it became a problem as soon as teams wanted more people talking to agents directly.
A product manager who wants to ask about a feature’s implementation should not need access to integration credentials and billing settings to do it. A QA engineer who messages Dawn in a Slack DM should not have that conversation show up in a shared workspace view. These are basic expectations, and Dawn was not meeting them.
This release fixes both.
Invite Your Team Without Handing Over the Keys
Dawn workspaces now have a teammate role. Teammates can talk to agents, start threads, attach files, and browse their own conversation history. They cannot change workspace settings, manage integrations, configure channels, or touch billing.
That means a workspace owner can invite the broader team — product, QA, support, design, whoever needs answers — and those people get a clean, focused experience built around asking questions and getting answers. They see the agents available to them, their own conversations, and nothing else.
The role is scoped per workspace, so the same person can be an owner in one workspace and a teammate in another. Access stays precisely where it should be.
A Richer Experience in the Web App
Teammates do not need access to the web app to use Dawn. The agent works the same way through Slack, Teams, Telegram, or any other connected channel. But the native web app offers a richer experience for people who want it.
The web interface renders Markdown, code blocks, tables, and structured agent outputs with more fidelity than most external chat platforms. Longer answers, formatted reports, and detailed explanations are easier to read and navigate in the browser than in a Slack thread or a Telegram message. For teammates who interact with Dawn frequently, having direct access to the app can be a noticeable improvement over working entirely through an external channel.
This is not a requirement — it is an option. Teams can choose the mix that works for them. Some people will prefer staying in Slack. Others will appreciate having the web app available for longer or more detailed conversations.
Private Conversations Across Every Channel
The other half of this release is direct message support.
Until now, Dawn only worked in shared channels. If someone wanted to ask a question, they had to do it in a place where the rest of the team could see it. That is fine for many interactions, but not all of them. Sometimes the question is sensitive. Sometimes someone is just exploring and does not want to broadcast half-formed thoughts to the whole channel.
Dawn now supports private conversations across Slack DMs, Telegram private chats, Teams personal messages, and Discord direct messages. When someone messages Dawn directly, that conversation stays private. It persists, so the thread picks up where it left off if someone comes back to it days later. It is auditable, so workspace owners still have operational visibility. But it does not appear in the shared conversation view.
That is the behaviour people already expect from direct messages in any other tool. Dawn now delivers it consistently across every channel type.
Less Noise in Shared Channels
Private conversations are not just about privacy. They also reduce noise.
Not every question someone asks Dawn needs to be visible to the whole team. Quick lookups, exploratory questions, half-formed ideas — these are useful interactions, but they clutter a shared channel when they happen dozens of times a day. Moving those conversations into DMs keeps shared channels focused on the discussions that actually benefit from visibility, while individuals still get the answers they need.
This works the same way across every channel Dawn supports. A private Slack DM, a Telegram private chat, a Teams personal message, or a thread in the web app — all of them keep the conversation between the person and the agent without adding to the noise in shared spaces.
What This Means in Practice
A few things change for teams using Dawn day to day.
Workspace owners can now open Dawn up to a much larger group of people without worrying about what those people might accidentally see or change. Inviting a teammate is low-risk because the role boundary is clear and narrow.
People who prefer to talk to Dawn privately — whether because the question is sensitive, because they are just exploring, or because a DM is simply more convenient — can do that on any supported channel and know the conversation is theirs. Shared channels stay cleaner as a result.
And for people who want a better reading experience for longer or more structured responses, the web app is now available without requiring admin access.
What Comes Next
This release makes Dawn usable by more of the team, in more natural conversation modes, without weakening the operational model that owners and managers rely on. The next step is making the teammate experience richer — better thread search, notification preferences, and agent discovery — as the teammate audience grows.