🎯 What is it?

Workspace admins now have access to a comprehensive analytics dashboard directly within Dust, plus a new public API endpoint for programmatic data access. The dashboard provides real-time visibility into adoption metrics (DAU/WAU/MAU), activity trends (messages, conversations), usage breakdown by source (web, Slack, extension, API), tool usage patterns, and top-performing agents. Each chart supports CSV export and offers flexible time ranges (7, 15, 30, or 90 days).

For teams that need to integrate Dust data into their own business intelligence tools, the new GET /api/v1/w/{wId}/analytics/export endpoint enables programmatic access to 7 data tables: usage metrics, active users, sources, agents, users, skill usage, and tool usage.

💡 Why is it useful?

Enterprise teams need self-service visibility into how Dust is being adopted across their organization to measure ROI and drive engagement. Until now, getting this data required manual CSV exports or reaching out to Customer Success for custom reports. This brings Dust's analytics capabilities in line with enterprise expectations for modern SaaS tools.

✨ Concrete Use Cases

Here's how you could use it:

Executive reporting: Export monthly adoption metrics to include in your quarterly AI transformation reports, showing DAU/MAU trends and demonstrating ROI to leadership.

Usage optimization: Identify which agents are most popular and which sources drive the most engagement, then use those insights to optimize your Dust rollout strategy and training programs.

BI integration: Pipe Dust analytics data into your existing Tableau, Looker, or PowerBI dashboards alongside other tools to create a unified view of productivity tool adoption.

📈 Benefits for you

• Self-service insights: No more waiting for manual reports—get instant visibility into adoption patterns

• Data-driven decisions: Use concrete metrics to guide your Dust rollout strategy

• Flexible export: Download charts as CSV or pull data programmatically via API

• Executive-ready: Generate adoption reports that demonstrate value to stakeholders

🚀 How to access it?

The analytics dashboard is available now to all workspace admins across all plans. Access it from your workspace admin panel. For API access, refer to the documentation for the new /api/v1/w/{wId}/analytics/export endpoint.

⚠️ API Deprecation Notice

📌 Context

The legacy analytics endpoints /api/v1/w/{wId}/usage and /api/v1/w/{wId}/workspace-usage are now deprecated and will be sunset on June 1, 2026.

🔄 Impact on Dust

We've built a new, more comprehensive analytics API that supersedes these legacy endpoints, providing richer data and better functionality.

👤 Impact for you

If you or your team are using the old endpoints: You'll need to migrate to the new /api/v1/w/{wId}/analytics/export endpoint before June 1, 2026. The new endpoint is a strict superset—it covers everything the old endpoints provided plus adds skill usage, tool usage, and detailed per-agent and per-user breakdowns.

If you're not using these endpoints: No impact—no action needed.

✅ Actions required

• Review your integrations: Check if any of your systems or scripts are calling /api/v1/w/{wId}/usage or /api/v1/w/{wId}/workspace-usage

• Plan your migration: Update those integrations to use the new /api/v1/w/{wId}/analytics/export endpoint before June 1, 2026

• Reach out if needed: If you need assistance with migration, contact your Customer Success team

Better Slack responses for Dust agents

Three improvements to how Dust agents respond in Slack, shipping together.

🔄 Smoother streaming

Agent responses now appear in real time as they're being generated, using Slack's native streaming. The experience feels faster and more alive, no more waiting for a full response to land before you can start reading !

🔎 See what your agent is doing

While an agent works, a live progress indicator shows which tools it's using and what it's doing with them. For web searches, you can see the query it ran. For browsing, you can see the sites it visited and the sources it pulled from. Once the agent is done, the indicator disappears cleanly.

✨ Better formatted responses

Tables, dividers, and code blocks now render properly in Slack. Agents that output structured content like pipeline summaries, incident reports, or side-by-side comparisons will now display the way they were meant to, without workarounds.

⚠️

Responses that include file uploads use the previous format for now.

🔥 Concrete Use Cases

All your current slack use cases, enhanced !

🚀 How to access it?

This feature is rolling out progressively to all Slack users this week. No action required on your part, you'll automatically see these improvements in your Slack workspace when they're available.

🎯 What is it?

We've released a new official GitHub Action called dust-github-action that lets you manage your Dust Skills and Agent configurations directly from your Git repository. You can now version-control your Dust setup, review changes through pull requests, and automatically sync your workspace from CI/CD pipelines.

💡 Why is it useful?

Managing Dust configurations through code gives you the same benefits you already get with your application code: change history, peer review, rollback capabilities, and automation. Instead of manually updating agents and skills in the Dust interface, you can define them in your repository and let your CI pipeline keep everything in sync. This is particularly valuable for teams that want to maintain consistency across workspaces, review configuration changes before deployment, or integrate Dust setup into their existing development workflows.

⚙ How does it work?

The GitHub Action provides methods to "upsert" (create or update) Skills and Agent configurations from your repository into your Dust workspace. When you push changes to your repo or merge a PR, the action automatically applies those configuration changes to your workspace.

✨ Concrete Use Cases

Here's how you could use it:

Development workflow: Define your agents in YAML files in your repo, have teammates review changes in pull requests, then automatically deploy approved configurations to your production Dust workspace when merged to main.

Multi-workspace management: Maintain a single source of truth for your agent configurations and sync them across development, staging, and production Dust workspaces using different GitHub Actions workflows.

Audit & rollback: Track every change to your Dust setup in Git history, see who made what changes and why, and easily roll back to previous configurations if needed.

📈 Benefits for you

• Better collaboration: Review agent and skill changes through pull requests before they go live

• Version control: Full history of all configuration changes with the ability to roll back

• Automation: Reduce manual work by syncing configurations automatically from CI

• Consistency: Keep multiple workspaces aligned using the same configuration source

• Integration: Fits into your existing development workflows and tooling

🚀 How to access it?

The GitHub Action is available now for all workspace admins and developers using GitHub Actions. Check out the repository and documentation to get started: https://github.com/dust-tt/dust-github-action

The feature is in General Availability (GA) and ready for production use.

🎯 What is it?

You can now choose which email address to send from when using Dust agents with the Gmail tool. If you have aliases configured in your Gmail account (like [email protected] or [email protected]), agents can now send emails from these addresses instead of only your personal email.

💡 Why is it useful?

Many professionals use email aliases to represent teams, departments, or shared inboxes. Until now, when an agent sent an email on your behalf, it could only use your primary Gmail address. This created limitations when you needed to maintain a specific professional identity or represent a team.

⚙️ How does it work?

When you ask an agent with the Gmail tool to send an email, you can now specify which of your configured Gmail aliases to use as the sender address. The agent will send the email from that alias, as long as it's properly set up in your Gmail account.

✨ Concrete Use Cases

Here's how you could use it:

Customer Support: Ask an agent to craft and send responses from your [email protected] alias, maintaining consistency in customer communications while saving time on routine replies.

Team Communications: Have an agent send project updates or meeting summaries from your team's shared email address (like [email protected]), ensuring all correspondence appears to come from the team rather than an individual.

📈 Benefits for you

• Professional consistency: Maintain the right email identity for each context

• Team representation: Send on behalf of groups or departments

• Time savings: Automate email tasks without losing control over sender identity

• Better organization: Keep communications aligned with your existing email structure

🚀 How to access it?

This feature is automatically available if you're using the Gmail tool. Simply ensure your aliases are configured in your Gmail account settings, then specify which address you'd like to use when asking an agent to send an email.

🎯 What is it?

Dust now includes a "Discover Skills" feature that allows agents to automatically find and use relevant skills from your workspace. Builders can flag specific skills as "discoverable," making them available to global agents like @dust and @deep-dive without manual configuration.

💡 Why is it useful?

Previously, if you wanted an agent to use a specific skill, you had to manually configure it for each agent. This created friction and meant many useful workspace skills went underutilized. With discoverable skills, your agents can now intelligently tap into your organization's collective capabilities, improving the baseline experience for everyone in your workspace.

⚙️How does it work?

Builders can mark their skills as "discoverable" when creating or editing them. Once flagged, these skills become available to global agents, which can automatically detect when a skill is relevant to a user's request and activate it on the fly.

✨ Concrete Use Cases

Here's how you could use it:

Sales team collaboration: A sales ops builder creates a "CRM Integration" skill and marks it discoverable. Now when anyone asks @dust about customer data, the agent automatically uses that skill without individual setup.

Knowledge sharing: Your engineering team builds a "Code Review Helper" skill. Mark it as discoverable, and @deep-dive can leverage it whenever someone asks technical questions, instantly improving responses across the workspace.

📈 Benefits for you

• Zero configuration: End users get access to powerful skills without any setup

• Better agent responses: Global agents like @dust deliver more accurate, context-aware answers by tapping into workspace expertise

• Increased skill adoption: Your team's best skills get used more widely, maximizing ROI on skill development

• Improved baseline experience: Everyone in the workspace benefits from collective knowledge automatically

🚀 How to access it?

For Builders: When creating or editing a skill, look for the new "Make discoverable" option and enable it for skills you want to share workspace-wide.

For Users: Simply use @dust or @deep-dive as usual - they'll automatically discover and leverage relevant skills when needed.

🎯 What is it?

You can now create your own triggers on every agent you have access to, including default agents like dust and deep-dive. Triggers allow you to automate agent interactions based on specific events or conditions, extending automation beyond just the agents you've built yourself.

💡 Why is it useful?

Previously, trigger creation might have been limited to agents you owned or edited. We believe that if you can talk to an agent, you should be able to automate it. This opens up powerful automation possibilities across your entire workspace, letting you leverage any agent in your automated workflows.

⚙ How does it work?

Create triggers directly from the Agent Details side panel of any agent you want to automate. Once created, all your triggers are centralized in your profile page where you can easily manage and monitor them.

✨ Concrete Use Cases

Here's how you could use it:

Automated research digest: Create a trigger on the deep-dive agent to automatically compile weekly competitive intelligence reports every Monday morning, even though you don't own that agent.

Team notification workflows: Set up triggers on shared team agents to automatically notify specific channels when certain conditions are met, without needing editor permissions on those agents.

Cross-agent automation: Build workflows that chain together multiple shared agents via triggers, creating sophisticated automation pipelines using agents created by different people across your organization.

📈 Benefits for you

• Democratized automation: Automate any agent you use, not just the ones you built

• Centralized management: Find and control all your triggers in one place on your profile page

• Better collaboration: Leverage agents built by colleagues in your automated workflows

• Transparency: Agent editors can see and audit all triggers on their agents; admins maintain full oversight

🚀 How to access it?

1. Navigate to any agent you have access to

2. Open the Agent Details side panel

3. Create your trigger with your desired configuration

4. Manage all your triggers from your profile page

Agent editors can view and audit all triggers created on their agents directly in the builder. Workspace admins can delete any trigger if needed.

🎯 What is it?

You can now configure a single API key to work across multiple spaces in your workspace, instead of being limited to one space at a time. This gives you more granular control over how integrations access your Dust environment.

💡 Why is it useful?

Previously, if you wanted an integration to access multiple spaces, you had two options: either give it workspace-wide access (too permissive) or create separate API keys for each space (too complex). This new capability follows the principle of least privilege—you can grant access to exactly the spaces an integration needs, nothing more and nothing less.

⚙️ How does it work?

When creating or editing an API key in the admin UI, you can now select multiple spaces that the key should have access to. The permission resolution has been updated to handle this multi-space access smoothly.

✨ Concrete Use Cases

Here's how you could use it:

Export shared agents: You have an agent shared across 3 different team spaces (Sales, Marketing, Customer Success). You can now create one API key scoped to these 3 spaces to export or sync that agent's data, instead of managing 3 separate keys.

Controlled cross-team integration: Your data pipeline needs to access specific spaces (Finance and Legal) but not others. You can create a single API key with access to only those two spaces, maintaining security while simplifying key management.

📈 Benefits for you

• Better security: Apply least-privilege principles without operational complexity

• Simpler management: One key for multiple spaces instead of juggling multiple keys

• Unlock new workflows: Run integrations across controlled sets of spaces that weren't practical before

🚀 How to access it?

This feature is already live for all workspace admins. When you create or manage API keys in your workspace admin panel, you'll see the option to select multiple spaces. All existing API keys have been automatically migrated, so nothing changes unless you want to adjust the configuration.

Salesforce MCP tool can now create and update objects

🎯 What is it?

The Salesforce MCP tool has evolved beyond read-only access. Your Dust agents can now create and update records directly in Salesforce—including companies, contacts, opportunities, notes, and other objects. This means agents can take actions on your behalf, not just retrieve information.

💡 Why is it useful?

This was one of our most frequently requested features. Until now, agents could read data from Salesforce but couldn't modify it, requiring you to manually update records after getting insights. With the introduction of medium stakes for agent actions, we've made it safe for agents to perform write operations with appropriate guardrails in place.

🚀 How to access it?

If you're already using the Salesforce MCP tool with your agents, the write capabilities are available after an admin checks the "Create Object" tool on, from the Admin>Tools>Salesforce menu

Simply ask your agent to create or update a Salesforce record—you'll be prompted to approve the action before it's executed.

If you haven't set up the Salesforce MCP tool yet, check our documentation or reach out to your Customer Success Manager to get started.

✨ Concrete Use Cases

Here's how you could use it:

Automated opportunity updates: After a sales call, an agent can analyze the conversation transcript and create follow-up tasks or update the opportunity stage in Salesforce directly.

Contact enrichment: When you share new information about a prospect, an agent can automatically create or update the contact record with relevant details like job title, company, or notes from your conversation.

Activity logging: Agents can create notes or log activities in Salesforce after customer interactions, ensuring your CRM stays up-to-date without manual data entry.

📈 Benefits for you

• Save time by eliminating manual data entry between Dust and Salesforce

• Maintain data accuracy with real-time updates to your CRM

• Enable end-to-end workflows where agents can both analyze and act on Salesforce data

• Stay in control with medium stakes approval for all write operations

🎯 What is it?

You can now interact with your Dust agents directly via email. Simply send or forward an email to [email protected] and your agent will process it and reply back to you. This works just like talking to an agent in Slack or the web app, but right from your inbox.

💡 Why is it useful?

Many teams work primarily in email—customer support threads, vendor communications, contracts, bug reports. Until now, you had to switch to Dust's web app or Slack to get help from your agents. With email integration, agents meet you where you already work, making it faster to get answers, draft replies, or process information without context-switching.

⚙ How does it work?

Once enabled in your workspace settings, you can send or forward emails to any agent using the format [email protected]. The agent processes your request and replies only to you (the sender). All conversations triggered by email are accessible in the Dust web app, just like agent conversations from Slack or Teams. If an agent needs authorization to use a specific tool, you'll receive a validation email with secure allow/decline links.

✨ Concrete Use Cases

Here's how you could use it:

Customer Support: Forward a customer complaint to your support agent and ask it to summarize the issue and suggest a reply draft.

Contract Review: Send a vendor agreement to a specialized legal/compliance agent and get a quick analysis without leaving your email thread.

Internal Workflows: CC an agent on an internal discussion thread and ask it to extract action items, create tickets, or draft follow-up communications.

Bug Triage: Forward a bug report from a client to your technical agent for initial analysis and categorization.

📈 Benefits for you

• Faster workflows: No need to copy-paste email content into Dust—just forward and ask

• Stay in context: Get agent help without leaving your inbox

• Flexible collaboration: Use agents as you would a colleague—forward, CC, or send directly

• Consistent experience: Same agent capabilities as Slack or web, accessible from email conversations in Dust

🚀 How to access it?

This feature is opt-in. To enable it:

1. Go to Workspace Settings → Capabilities → Email agents

2. Turn on the feature

3. Start emailing your agents at [email protected]

📖 Full documentation available here: https://docs.dust.tt/docs/email-agents

🔒 Security note: Just as you wouldn't click suspicious links in emails, avoid forwarding suspicious or untrusted emails to agents to minimize prompt injection risks.

🎯 What is it?

Admins can now customize which permissions (OAuth scopes) are requested when installing Microsoft MCP tools. When setting up tools like Outlook Mail, Outlook Calendar, Microsoft Drive, Excel, or Teams, you can uncheck optional permissions such as write access, shared mailboxes, or contacts access. Once configured, these restrictions apply automatically to all user connections in your workspace.

💡 Why is it useful?

Many enterprise organizations have strict Azure AD policies that require minimizing permission requests. Previously, MCP tools requested all possible scopes by default, which could trigger lengthy admin consent processes or even block installation entirely. This feature gives you granular control over the permission surface, making it easier to align Dust with your organization's security policies and get approvals faster.

⚙ How does it work?

During the MCP tool installation flow, admins will see a list of available OAuth scopes with checkboxes. Simply uncheck any optional permissions your organization doesn't need. Dust will only request the scopes you've selected, and all users in your workspace will inherit these restrictions when they connect their personal Microsoft accounts to the agent.

✨ Concrete Use Cases

Here's how you could use it:

Read-only access: Your security team only wants agents to read emails and calendar events, not send or modify them. Uncheck write permissions during Outlook Mail and Calendar installation.

No shared mailbox access: Your organization doesn't use shared mailboxes and your IT policy forbids requesting that permission. Uncheck the shared mailbox scope when installing Outlook Mail to avoid unnecessary admin consent blockers.

📈 Benefits for you

• Faster deployment: Reduce admin consent friction by requesting only the minimum required permissions

• Better security posture: Minimize the permission surface and align with your zero-trust policies

• Greater control: Tailor each tool's access level to match your organization's specific needs

🚀 How to access it?

This feature is automatically available when installing or reconfiguring Microsoft MCP tools (Outlook Mail, Outlook Calendar, Microsoft Drive, Excel, Teams). Workspace admins will see the configurable scopes during the installation flow. If you need this capability for other MCP tools, reach out to your Customer Success Manager.