docs: document Lightdash support access toggle#716
Merged
Conversation
Contributor
🤖 Documentation BotStatus🔗 Broken Links (Manual Fix Required)Click to view details |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
rephus
approved these changes
May 28, 2026
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
Adds a new admin reference page documenting the per-organization consent toggle that lets the Lightdash support team impersonate users while assisting with a support request.
Changes
references/workspace/support-impersonation.mdxcovering when to enable the toggle, how it works, who can change it, and how to turn it on or off from organization settings.docs.json, next to the existing user impersonation reference.Context
Triggered by lightdash/lightdash#23584, which introduces a
Lightdash support accesscard in organization settings with an opt-in toggle (off by default). The new doc gives admins guidance on when and how to use it, and clarifies how it differs from the existing in-organization user impersonation feature.