docs: document org-level scheduled delivery download link expiry

Author: mintlify[bot]

guides/how-to-create-scheduled-deliveries.mdx

@@ -10,7 +10,7 @@ If your Lightdash organization has [Slack](/references/workspace/adding-slack-in
 
 This means old emails or Slack shares will have broken images and there is not an option to retrieve them. If you want to keep the sent files, it's best to download them from the scheduled delivery.
 
-Self-hosted instances can [configure download link expiration](#configuring-download-link-expiration) per channel.
+Organization admins can [change the default expiry](#configuring-download-link-expiration) and optionally set a different expiry per channel (Slack, email, MS Teams).
 
 </Info>
 
@@ -250,4 +250,13 @@ For example:
 
 ## Configuring download link expiration
 
-By default, download links in scheduled deliveries expire after 3 days. Self-hosted instances can adjust this globally or per channel (email, Slack, MS Teams) using [persistent download URL environment variables](/self-host/customize-deployment/environment-variables#persistent-download-urls).
+By default, download links in scheduled deliveries expire after 3 days. Organization admins can change this in **Organization settings → Scheduled deliveries**.
+
+- **Download link expiry** — how many days a scheduled delivery's download links stay valid before they expire. This value applies to every delivery channel by default.
+- **Set a different expiry for specific channels** — toggle this on to override the default for individual channels (Slack, email, MS Teams). When off, every channel uses the default expiry above.
+
+Click **Save** to apply your changes. New expiry values take effect on the next scheduled delivery run.
+
+<Note>
+  Self-hosted instances can also set these values globally using [persistent download URL environment variables](/self-host/customize-deployment/environment-variables#persistent-download-urls). Organization-level settings take precedence when configured.
+</Note>