[DOCS-XXXXX] Add Authorize Private Actions - #39050
Draft
irving-santiago wants to merge 1 commit into
Draft
Conversation
This was referenced Aug 10, 2026
Author
1 task
This was referenced Aug 10, 2026
Contributor
Preview links (active after the
|
This comment has been minimized.
This comment has been minimized.
… ordering convention
irving-santiago
force-pushed
the
irving.santiago/par-ep-06-authorize
branch
from
August 10, 2026 12:15
2eb57ef to
828cb5b
Compare
irving-santiago
force-pushed
the
irving.santiago/par-ep-05-enroll-runner
branch
from
August 10, 2026 12:15
36004d3 to
4002819
Compare
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
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?
Fixes DOCS-XXXXX
Adds a new "Authorize Private Actions" page comparing the two authorization models (Connections vs. Execution Policies) and explaining which one applies to a given runner based on its ownership.
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Claude Code carried this page's content over from a pre-drafted, QA-verified draft, ran Vale, and fixed an invalid front-matter YAML value and a couple of style-guide word-choice issues. After a post-implementation structure review against the original plan, also fixed 3 places where the draft listed Connections before Execution Policies (a section order, a comparison table's columns, and a bullet list), which violated this project's standing ordering convention (Execution Policies/ownerless before Connections/owned).
Additional notes