CPS: Dashboard-level scope and panel-level custom scope badge#5428
Merged
florent-leborgne merged 25 commits intocps-tech-previewfrom Mar 23, 2026
Merged
CPS: Dashboard-level scope and panel-level custom scope badge#5428florent-leborgne merged 25 commits intocps-tech-previewfrom
florent-leborgne merged 25 commits intocps-tech-previewfrom
Conversation
Add a section explaining that alerting rules use the space-level CPS scope (not a per-rule setting), and that the project picker is read-only on rule pages. Closes #688 Made-with: Cursor
Contributor
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Made-with: Cursor
Add a new "Cross-project search scope" section to the dashboard usage page covering dashboard-level CPS scope storage and per-panel custom CPS scope badges. Also add the CPS settings option to the dashboard creation page and a brief CPS badge section to the panel management page. Closes #690, closes #691 Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
f15fec0 to
9f4cfb7
Compare
The save modal label is being updated from "Store project routing with dashboard" to "Store CPS scope with dashboard" in elastic/kibana#259142. Made-with: Cursor
Remove alerting, observability rules, and security detection rules CPS content that was added by mistake. This PR focuses on dashboard-level CPS scope and panel-level custom CPS scope badge only. Made-with: Cursor
- using.md (viewer): keep scope selector and badge explanation, remove store instructions, link to creator page - create-dashboard.md (creator): expand store CPS scope into a full section with settings flyout and save modal instructions - manage-panels.md (creator): explain why the badge appears, which panel types support it, and how to edit from the popover Made-with: Cursor
Nest the CPS section as a subsection of "Search and filter your dashboard data" with a verb-led heading matching sibling sections. Rewrite content from the viewer's perspective: what they see, what they can change, and why some panels behave differently. Made-with: Cursor
The viewer's scope selector controls which projects are queried by default, not the creator's setup. Remove misleading sentence and reframe around what the viewer sees and can do. Made-with: Cursor
Made-with: Cursor
Structure the CPS section as default behavior first, then two bullet points for the outlier cases (stored scope, custom badge). Fix the inline anchor to use valid MyST target syntax. Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
List all save options as bullet points for scannability. Move ownership note under Permissions. Replace "modal" with plain language. Made-with: Cursor
The setting is already explained in both step 5 (settings flyout) and step 6 (save options). The standalone section was duplicating that content. Update cross-links accordingly. Made-with: Cursor
The badge appears automatically and requires no panel management action. The viewer perspective is already covered in using.md, and the Edit action is a shortcut to the existing Edit visualization flow. Made-with: Cursor
florent-leborgne
added a commit
to elastic/kibana
that referenced
this pull request
Mar 24, 2026
## Summary The dashboard settings flyout uses **"Store CPS scope with dashboard"** but the save modal uses **"Store project routing with dashboard"**. This aligns the save modal label and tooltip to use the same user-facing CPS terminology as the settings flyout. Additionally, both the save modal tooltip and the settings flyout help text are aligned to use the same concise phrasing, spelling out "cross-project search (CPS)" instead of just "CPS". ### Changes - Save modal label: "Store project routing with dashboard" → "Store CPS scope with dashboard" - Save modal tooltip: Aligned with settings flyout phrasing, spelling out "cross-project search (CPS)" - Settings flyout help text: Shortened and aligned with the save modal tooltip ### Context Found while reviewing CPS documentation ([docs-content#5428](elastic/docs-content#5428)). The inconsistency was spotted by cross-referencing the two UI surfaces against the Kibana source. Made with [Cursor](https://cursor.com)
Contributor
|
LGTM 👌🏼 |
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 CPS documentation to the dashboard pages, split by audience:
For dashboard viewers (
using.md):For dashboard creators (
create-dashboard.md):Closes elastic/docs-content-internal#690
Closes elastic/docs-content-internal#691
Test plan
explore-analyze/dashboards/usingandexplore-analyze/dashboards/create-dashboardapplies_totags render properly (serverless preview / stack unavailable)Generative AI disclosure
Tool(s) and model(s) used: Claude (Cursor)
Made with Cursor