Static egress IP page, transcription formats and limits, Slack message attribution

docs.json

@@ -350,6 +350,7 @@
             "group": "Tools management",
             "pages": [
               "docs/user-documentation/admins/tools-management/adding-an-mcp-server",
+              "docs/user-documentation/admins/tools-management/static-egress-ips",
               "docs/user-documentation/admins/tools-management/personal-vs-shared-credentials",
               {
                 "group": "Salesforce",
@@ -2257,6 +2258,14 @@
     {
       "source": "/docs/user-documentation/pods/getting-started",
       "destination": "/docs/user-documentation/getting-started/dust-rollout-guide"
+    },
+    {
+      "source": "/changelog/static-ip-for-custom-mcp-server-calls",
+      "destination": "/docs/user-documentation/admins/tools-management/static-egress-ips"
+    },
+    {
+      "source": "/changelog/changelog-update-8",
+      "destination": "/docs/changelog"
     }
   ],
   "thumbnails": {

docs/changelog.mdx

@@ -742,7 +742,7 @@ The skill is discoverable and available to every user. Mention @dust and ask you
 
 🎯 What is it?
 
-A new speech-to-text tool is now available in Dust, allowing your agents to transcribe spoken content from both audio and video sources. You can transcribe content from supported URLs or by uploading files directly, with support for most common formats (mp3, mp4, wav, m4a, mov, webm, aac, flac, and more).
+A new speech-to-text tool is now available in Dust, allowing your agents to transcribe spoken content from both audio and video sources. Video content (mp4, mov, webinars, meeting recordings) is transcribed from URLs on supported platforms (YouTube, Loom, Zoom, Google Drive, and more). Audio files (mp3, m4a, wav, ogg, webm) up to 100 MB can also be uploaded directly to the conversation.
 
 💡 Why is it useful?
 

docs/user-documentation/admins/connections-management/snowflake.mdx

@@ -47,7 +47,7 @@ Follow the appropriate setup instructions below based on your chosen authenticat
 
 ### Setup on Snowflake's side
 
-Note: For configuring access to Snowflake, you may need to whitelist the following Dust static IP: If you're in the US (routes start with [https://dust.tt](https://dust.tt)) the IP is `34.46.9.232`. For the EU customers (routes start with [https://eu.dust.tt](https://eu.dust.tt)) the IP is `35.195.191.222`
+Note: For configuring access to Snowflake, you may need to whitelist the following Dust static IP: If you're in the US (routes start with [https://dust.tt](https://dust.tt)) the IP is `34.46.9.232`. For the EU customers (routes start with [https://eu.dust.tt](https://eu.dust.tt)) the IP is `35.195.191.222`. See [Static egress IP addresses](/docs/user-documentation/admins/tools-management/static-egress-ips) for details on when static IPs apply.
 
 
 <Info>

docs/user-documentation/admins/tools-management/static-egress-ips.mdx

@@ -0,0 +1,25 @@
+---
+title: "Static egress IP addresses"
+---
+
+Some security teams need to whitelist Dust's outbound IP addresses in their firewall, for example to let Dust reach a remote MCP server or a Snowflake instance behind a network policy.
+
+## When Dust uses static IPs
+
+Dust routes outbound traffic through static egress IPs only in these two cases:
+
+- **Remote MCP servers** hosted on a domain verified for your workspace (Admin > People & Security > Verified domains). The MCP server hostname must belong to the verified domain itself, for example `mcp.acme.com` under a verified `acme.com`. A host on a different domain, including a vendor's domain, is not covered.
+- **Snowflake connections**.
+
+All other outbound traffic (web search, browsing, other tools and connections) uses dynamic cloud IPs that can change at any time. Do not whitelist those.
+
+## The IP addresses
+
+| Region | Static egress IP |
+| --------------- | ---------------- |
+| US (`dust.tt`) | `34.46.9.232` |
+| EU (`eu.dust.tt`) | `35.195.191.222` |
+
+<Warning>
+These IPs are shared by all Dust workspaces. A firewall rule that allows them does not identify your workspace. Never rely on source IP alone to authenticate requests: keep authentication (bearer token or OAuth) enabled on your MCP server. IP whitelisting is a network-level restriction, not an identity guarantee.
+</Warning>

docs/user-documentation/agents/tools/slack-tools.mdx

@@ -117,6 +117,13 @@ Read all messages in a specific thread from public channels, private channels, o
 * Reference channels using \<#CHANNEL_ID> format
 * Never use plain names as they won't be parsed correctly
 
+## Message Attribution
+
+Messages posted by agents include a "Sent via [agent] on Dust" footer by default.
+
+- Personal Slack tools: agents can omit the footer only if a workspace admin has enabled footer removal in the workspace settings. When the setting is off (the default), the footer is always shown.
+- Slack Bot tool: messages are posted by the Dust Slack app, so authorship is already visible at the app level. Agents can control the footer per message with the `showSentByFooter` parameter, which defaults to on.
+
 ## Limitations & Considerations
 
 * Standard Slack API limits apply

docs/user-documentation/getting-started/faq/file-size-limits.mdx

@@ -5,8 +5,14 @@ title: "File size limits"
 
 In-conversation file uploads:
 
-- Images: 5 MB
-- Audio files: 25 MB
+- Images: 20 MB
+- Audio files: 100 MB
 - Data files (txt, pdf, doc, json, etc.): 50 MB
 - Code files: 50 MB
 - Delimited files (csv, tsv, xls, xlsx): 50 MB
+
+## Supported audio formats
+
+Direct in-conversation upload supports audio files only: `mp3`, `m4a`, `wav`, `ogg`, and `webm`.
+
+Video files (`mp4`, `mov`) cannot be uploaded directly to a conversation. To transcribe video content, give the agent a link from a supported platform (YouTube, Vimeo, Loom, Zoom, Google Drive, SharePoint, OneDrive, Dropbox, Slack, and most meeting recording platforms), or extract the audio track and upload that instead.