(Account Management) Cross-Org Visibility best practices #35895
Open
OliviaShoup wants to merge 1 commit intomasterfrom
Open
(Account Management) Cross-Org Visibility best practices #35895OliviaShoup wants to merge 1 commit intomasterfrom
OliviaShoup wants to merge 1 commit intomasterfrom
Conversation
Contributor
Preview links (active after the
|
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.
What does this PR do? What is the motivation?
This PR adds info about Service Accounts to the Cross-Organization Visibility page. It also recommends the use of Service Accounts to create and manage Cross-Org Connections.
Resolves https://datadoghq.atlassian.net/browse/DOCS-13759
Merge instructions
Merge readiness:
AI assistance
I used Cursor with Claude Sonnet 4.6 to help turn the Jira notes into the first draft.
Additional notes