CPS-related edits to existing pages by marciw · Pull Request #5560 · elastic/docs-content

marciw · 2026-03-18T23:52:48Z

Summary

Updates various existing pages with info related to cross-project search. See also the D3 and D3A updates in the docs plan (Gdoc)

Generative AI disclosure

Did you use a generative AI (GenAI) tool to assist in creating this contribution?

Yes
No

Tool(s) and model(s) used:
Claude opus 4.6, Cursor composer

github-actions · 2026-03-18T23:54:02Z

Vale Linting Results

Summary: 1 warning, 1 suggestion found

⚠️ Warnings (1)

File	Line	Rule	Message
reference/glossary/index.md	169	Elastic.DontUse	Don't use 'just'.

💡 Suggestions (1)

File	Line	Rule	Message
reference/glossary/index.md	500	Elastic.Repetition	"makes" is repeated.

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.

naj-h

left 1 comment, the rest LGTM!

naj-h · 2026-03-25T13:14:28Z

reference/glossary/index.md


 $$$glossary-tag$$$ tag
-:   A keyword or label that you assign to {{kib}} saved objects, such as dashboards and visualizations, so you can classify them in a way that is meaningful to you. Tags makes it easier for you to manage your content. See [Tags](/explore-analyze/find-and-organize/tags.md).
+:   A keyword or label that you assign to {{kib}} saved objects, such as dashboards and visualizations, so you can classify them in a way that is meaningful to you. Tags makes it easier for you to manage your content. In {{serverless-full}}, you can use project metadata tags in [{{cps}}es](/explore-analyze/cross-project-search.md). See [Tags](/explore-analyze/find-and-organize/tags.md).


This should be removed: Kibana tags on saved objects are not something you can use for CPS project routing. It's the Cloud project tags that we use

++ needs disambiguation with project tags in this definition instead

shainaraskas · 2026-03-24T20:01:11Z

deploy-manage/manage-spaces.md


+:::{note}
+:applies_to: serverless: preview
+If your organization uses [{{cps}}](/explore-analyze/cross-project-search.md) ({{cps-init}}) in {{serverless-full}}, you can set the {{cps-init}} scope for a space. This setting determines the default scope for cross-project searches: origin only, or origin + all linked projects. For details, refer to [Set the default {{cps-init}} scope for a space](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#cps-default-search-scope).


maybe a hint here that you can set this up ahead of time if you're planning to start using CPS

shainaraskas · 2026-03-24T20:04:55Z

deploy-manage/manage-spaces.md


 When a role is assigned to *All Spaces*, you can’t remove its access from the space settings. You must instead edit the role to give it more granular access to individual spaces.

+:::{note}


this is in the wrong spot. access to a space is "can I get to the space" and cps scope of a space is an attribute of the way the space works - closer to the "create a space" section or "Customize Kibana's home page"

maybe it gets its own h2 because it's closer to the other h2s lower on the page. could reuse this stuff

shainaraskas · 2026-03-24T20:23:51Z

deploy-manage/deploy/elastic-cloud/project-settings.md

 * The team or department that uses it: `dept:finance`, `dept:marketing`, `dept:engineering`
 * The environment type: `env:dev`, `env:staging`, or `env:prod`

+{applies_to}`serverless: preview` You can also use tags in {{cps}} project routing expressions. For details, refer to [](/explore-analyze/cross-project-search/cross-project-search-tags.md).


would integrate this into the general value prop for project tags: categorize and organize, and search by project attributes in cps project routing expressions (i.e. above not below)

shainaraskas · 2026-03-25T18:07:11Z

deploy-manage/remote-clusters.md

+::::{note}
+Remote clusters are not available in {{serverless-full}}. To search across more surfaces in {{serverless-short}}, use [{{cps}}](/explore-analyze/cross-project-search.md).
+::::


while this note is accurate, I think we need to at least acknowledge that we don't have a CCR replacement. we should also use config-side links because our audience on this page is admins

Suggested change

::::{note}

Remote clusters are not available in {{serverless-full}}. To search across more surfaces in {{serverless-short}}, use [{{cps}}](/explore-analyze/cross-project-search.md).

::::

::::{admonition} Alternatives for {{serverless-short}}

Remote clusters are not available in {{serverless-full}}.

* The equivalent of {{ccs}} in {{serverless-full}} is [{{cps}}](/deploy-manage/cross-project-search-config.md). {{cps-init}} does not require remote cluster configuration.

* A feature equivalent to cross-cluster replication is anticipated in a future release.

::::

shainaraskas · 2026-03-25T18:12:57Z

deploy-manage/security/_snippets/complete-security.md

 * Prevent unauthorized access with [password protection and role-based access control](/deploy-manage/users-roles.md).
 * Control access to dashboards and other saved objects in your UI using [Spaces](/deploy-manage/manage-spaces.md).
 * Connect a local cluster to a [remote cluster](/deploy-manage/remote-clusters.md) to enable [cross-cluster replication](/deploy-manage/tools/cross-cluster-replication.md) and [cross-cluster search](/explore-analyze/cross-cluster-search.md).
+* Set a default [{{cps}} scope](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#cps-default-search-scope) for a space and [manage user access to linked projects](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#manage-user-access). {applies_to}`serverless: preview`   
 * Manage [API keys](/deploy-manage/api-keys.md) used for programmatic access to Elastic.


think this is too granular here. CPS ultimately just reflects user access which is consistent throughout elastic cloud. you could elaborate on the spaces definition but not sure how to do so smoothly :/

Suggested change

* Prevent unauthorized access with [password protection and role-based access control](/deploy-manage/users-roles.md).

* Control access to dashboards and other saved objects in your UI using [Spaces](/deploy-manage/manage-spaces.md).

* Connect a local cluster to a [remote cluster](/deploy-manage/remote-clusters.md) to enable [cross-cluster replication](/deploy-manage/tools/cross-cluster-replication.md) and [cross-cluster search](/explore-analyze/cross-cluster-search.md).

* Set a default [{{cps}} scope](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#cps-default-search-scope) for a space and [manage user access to linked projects](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#manage-user-access). {applies_to}`serverless: preview`

* Manage [API keys](/deploy-manage/api-keys.md) used for programmatic access to Elastic.

* Prevent unauthorized access with [password protection and role-based access control](/deploy-manage/users-roles.md).

* Control access to dashboards and other saved objects in your UI using [Spaces](/deploy-manage/manage-spaces.md). If applicable, you can also set a [default CPS scope](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#cps-default-search-scope) for each space.

* Connect a local cluster to a [remote cluster](/deploy-manage/remote-clusters.md) to enable [cross-cluster replication](/deploy-manage/tools/cross-cluster-replication.md) and [cross-cluster search](/explore-analyze/cross-cluster-search.md).

* Manage [API keys](/deploy-manage/api-keys.md) used for programmatic access to Elastic.

shainaraskas · 2026-03-25T18:16:32Z

reference/glossary/index.md

 :   Searches [data streams](/reference/glossary/index.md#glossary-data-stream) and [indices](/reference/glossary/index.md#glossary-index) on [remote clusters](/reference/glossary/index.md#glossary-remote-cluster) from a [local cluster](/reference/glossary/index.md#glossary-local-cluster). See [Search across clusters](/explore-analyze/cross-cluster-search.md).

+$$$glossary-cps$$$ {{cps}} ({{cps-init}}) {applies_to}`serverless: preview`
+:   Searches across multiple {{serverless-full}} linked projects from a single origin project. See [{{cps-cap}}](/explore-analyze/cross-project-search.md).


I think we need a noun here. "A project configuration that allows you to" "A feature that allows you to link blah blah"

shainaraskas · 2026-03-25T18:24:13Z

deploy-manage/index.md

 * [](/deploy-manage/api-keys.md): Authenticate and authorize programmatic access to your deployments and {{es}} resources.
 * [](/deploy-manage/manage-connectors.md): Manage connection information between Elastic and third-party systems.
 * [](/deploy-manage/remote-clusters.md): Enable communication between {{es}} clusters to support [cross-cluster replication](/deploy-manage/tools/cross-cluster-replication.md) and [cross-cluster search](/explore-analyze/cross-cluster-search.md).
+* [Cross-project search](/deploy-manage/cross-project-search-config.md): Set up and manage [{{cps}}](/explore-analyze/cross-project-search.md) so users can search across multiple {{serverless-full}} projects at once. {applies_to}`serverless: preview` 


avoid using the term in the definition. this can be a little more sales-y I think. college try

Suggested change

* [Cross-project search](/deploy-manage/cross-project-search-config.md): Set up and manage [{{cps}}](/explore-analyze/cross-project-search.md) so users can search across multiple {{serverless-full}} projects at once. {applies_to}`serverless: preview`

* [Cross-project search](/deploy-manage/cross-project-search-config.md): Link multiple {{serverless-full}} projects to broaden the dataset users can query and visualize. {applies_to}`serverless: preview`

shainaraskas · 2026-03-25T18:26:48Z

deploy-manage/users-roles/serverless-custom-roles.md

 ::::{note}
-You cannot assign [run as privileges](elasticsearch://reference/elasticsearch/security-privileges.md#_run_as_privilege) in {{serverless-full}} custom roles.
+- You cannot assign [run as privileges](elasticsearch://reference/elasticsearch/security-privileges.md#_run_as_privilege) in {{serverless-full}} custom roles.
+- If your organization uses [cross-project search](/explore-analyze/cross-project-search.md) in {{serverless-short}}, assigned roles continue to apply. Users can work with data from [linked projects](/deploy-manage/cross-project-search-config.md#key-concepts) only if their assigned privileges already allow access to those projects. {applies_to}`serverless: preview` 


I'd like to see this as its own h2

reminds me that these pages need an edit:

https://www.elastic.co/docs/deploy-manage/users-roles/cloud-organization/user-roles
https://www.elastic.co/docs/deploy-manage/api-keys/serverless-project-api-keys (keys don't work for cps)
https://www.elastic.co/docs/deploy-manage/api-keys/elastic-cloud-api-keys

CPS admin edits to existing pages

5cd77a0

marciw added 3 commits March 19, 2026 15:17

Add CPS scope to Manage spaces topic

c22ed70

Merge branch 'cps-tech-preview' into mw-cps-tech-preview

faaeb03

more CPS edits to existing pages

e7d5e64

marciw changed the title ~~[WIP] CPS admin edits~~ CPS-related edits to existing pages Mar 23, 2026

Merge branch 'cps-tech-preview' into mw-cps-tech-preview

517f671

marciw marked this pull request as ready for review March 23, 2026 22:26

marciw requested review from a team as code owners March 23, 2026 22:26

marciw requested a review from naj-h March 23, 2026 22:34

marciw assigned alisonelizabeth and unassigned alisonelizabeth Mar 23, 2026

marciw requested review from alisonelizabeth and shainaraskas March 23, 2026 22:35

naj-h reviewed Mar 25, 2026

View reviewed changes

shainaraskas reviewed Mar 25, 2026

View reviewed changes

Merge branch 'cps-tech-preview' into mw-cps-tech-preview

9b5d41e

shainaraskas reviewed Mar 25, 2026

View reviewed changes

shainaraskas mentioned this pull request Mar 26, 2026

CPS tech preview #5498

Draft


		When a role is assigned to All Spaces, you can’t remove its access from the space settings. You must instead edit the role to give it more granular access to individual spaces.

		:::{note}

	* [Cross-project search](/deploy-manage/cross-project-search-config.md): Set up and manage [{{cps}}](/explore-analyze/cross-project-search.md) so users can search across multiple {{serverless-full}} projects at once. {applies_to}`serverless: preview`
	* [Cross-project search](/deploy-manage/cross-project-search-config.md): Link multiple {{serverless-full}} projects to broaden the dataset users can query and visualize. {applies_to}`serverless: preview`

Conversation

marciw commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Generative AI disclosure

Uh oh!

github-actions bot commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Vale Linting Results

Uh oh!

naj-h left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

marciw commented Mar 18, 2026 •

edited

Loading

github-actions bot commented Mar 18, 2026 •

edited

Loading

naj-h left a comment •

edited

Loading