docs: document org-level scheduled delivery link expiry#729
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document org-level scheduled delivery link expiry#729mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
🤖 Documentation BotStatus🔗 Broken Links (Manual Fix Required)Click to view details |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document the new organization-level Exporting settings that let admins configure scheduled-delivery download link expiry (base + per-channel overrides) from the UI.
Changes
Context
Source PR: lightdash/lightdash#23702 — adds per-org scheduled-delivery link expiry settings with per-channel overrides (Email, Slack, Microsoft Teams, Google Chat) and transparent persistent-URL escalation when an expiry exceeds the 7-day SigV4 limit. The env vars remain as fall-back defaults, so existing instances are unaffected.