[docs-agent] Document CPS-eligible tier gating for space project routing panel - #7861
Draft
github-actions[bot] wants to merge 1 commit into
Draft
[docs-agent] Document CPS-eligible tier gating for space project routing panel#7861github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summary
Adds a note to Manage access and scope for cross-project search explaining that the Cross-project search panel in space settings (create space and edit space pages) only appears for projects on a CPS-eligible pricing tier, and that a downgraded space retaining a non-default project routing value keeps the panel visible until the scope is reset to All projects. The tier requirements are cross-linked to the existing "projects available for linking" section rather than duplicated.
Triage rationale
The issue (#7635) was sufficiently specified: it names the exact page/section to edit, the exact behavior to document, and links Kibana PR elastic/kibana#278267. I verified the behavior directly against that PR's diff — specifically
edit_space_general_tab.tsx'scanReadProjectRouting(), which now checkscps?.isTierEligible === true || isCustomProjectRouting(space.projectRouting)— confirming both the tier-gating and the downgrade escape-hatch behavior described in the issue. The newCPS_TIER_ELIGIBLE_FEATUREinkbn-cps-common/pricing.tsconfirms eligible tiers are Security/Observability Complete, matching the tier requirement already documented incross-project-search-config.md#cps-compatibility, so the fix cross-links instead of restating the tier list.Drafting sources
AGENTS.md(cumulative docs, style, canonical-page principles)deploy-manage/cross-project-search-config/cps-config-access-and-scope.mddeploy-manage/cross-project-search-config.md(#cps-compatibilitytier requirements, reused via cross-link)edit_space_general_tab.tsxandkbn-cps-common/src/common/pricing.tsNote: The Elastic Docs MCP server (
elastic-docs) returned no available tools in this run, so contribution guidance was drawn from the repository's localAGENTS.md/contribute-docs content instead.Reader test
Closes #7635
This draft PR was produced autonomously by docs-agent-experimental in experimental mode.
Safe-output PRs do not trigger CI by default. A maintainer must trigger the required checks manually.