docs(security): per-repo product enablement is repository write level#11827
Merged
Conversation
Per-repository product enablement, including activating CI Insights, is
enforced at repository WRITE level via PUT /v1/products/{owner}/{repository}.
Only the org-level default-products configuration requires Integrations Admin.
Correct the security page so the documented model matches enforcement:
- Features Permissions: "Activate CI Insights on a repository" is write-level,
not Owner-only.
- Delegated Roles: Integrations Admin grants org-level default products and
third-party integrations, not per-repo product enablement; drop "activate
CI Insights" from CI Admin since per-repo activation is write-level, not a
delegated owner power.
- Tighten the Delegated Roles intro so its examples reference org-level
operations only.
Surfaced by HackerOne #3801915: a write collaborator activated CI Insights
and the reporter cited these rows as the owner-only boundary. The docs were
wrong; the access-control behavior is correct.
Fixes MRGFY-7644
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I90961aa435b34f468fec7921b6664bee5199e832
Contributor
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 👀 Review RequirementsWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
kozlek
approved these changes
Jun 15, 2026
remyduthu
approved these changes
Jun 15, 2026
Contributor
Merge Queue StatusQueued — the merge queue status continues in this comment ↓. |
Contributor
Merge Queue Status
This pull request spent 2 minutes 33 seconds in the queue, including 2 minutes 9 seconds running CI. Required conditions to merge
|
51 tasks
mergify
Bot
deleted the
devs/sileht/fix-security-docs-product-enablement-permissions/per-repo-product-enablement-repo-write-level--90961aa4
branch
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.
Per-repository product enablement, including activating CI Insights, is
enforced at repository WRITE level via PUT /v1/products/{owner}/{repository}.
Only the org-level default-products configuration requires Integrations Admin.
Correct the security page so the documented model matches enforcement:
not Owner-only.
third-party integrations, not per-repo product enablement; drop "activate
CI Insights" from CI Admin since per-repo activation is write-level, not a
delegated owner power.
operations only.
Surfaced by HackerOne #3801915: a write collaborator activated CI Insights
and the reporter cited these rows as the owner-only boundary. The docs were
wrong; the access-control behavior is correct.
Fixes MRGFY-7644
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com