CPS-related edits to existing pages

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

@@ -149,6 +149,8 @@ For example, you might tag a project with the following types of metadata:
 * 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).
+
 ### Create project tags
 
 1. In {{ecloud}}, select your project from the **Serverless projects** panel and click **Manage**.

deploy-manage/index.md

@@ -60,6 +60,7 @@ Learn how to secure your Elastic environment to restrict access to only authoriz
 * [](/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` 
 
 ## Administer and maintain
 

deploy-manage/manage-spaces.md

@@ -111,6 +111,10 @@ If you're managing an {{stack}} deployment, then you can also assign roles and d
 
 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}
+: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).
+:::
 
 ## Move saved objects between spaces [spaces-moving-objects]
 

deploy-manage/remote-clusters.md

@@ -28,6 +28,10 @@ Remote clusters are especially useful in two cases:
 :::{include} ./remote-clusters/_snippets/terminology.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).
+::::
+
 ## Security models and connection modes
 
 When configuring remote clusters, you can choose between two security models and two connection modes. Both security models are compatible with either connection mode.

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

@@ -4,5 +4,6 @@ As part of your overall security strategy, you can also do the following:
 * 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.
 ::::

deploy-manage/uninstall/delete-a-cloud-deployment.md

@@ -41,7 +41,12 @@ If you want to keep the snapshot for future purposes even after the deployment d
 
 ## Serverless
 
-To delete a {{serverless-full}} project:
+:::{note}
+:applies_to: serverless: preview
+You can't delete a project that's linked to a {{cps}} ({{cps-init}}) origin project. To delete a linked project, first [unlink](/deploy-manage/cross-project-search-config/cps-config-link-and-manage.md#cps-unlink-projects) it from every origin project it's connected to, then delete it.
+:::
+
+To delete an {{serverless-full}} project:
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
 2. Find your project on the home page in the **Serverless Projects** card and select **Manage** to access it directly. Or, select **Serverless Projects** to go to the projects page to view all of your projects.

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

@@ -20,7 +20,8 @@ Roles are a collection of privileges that enable users to access project feature
 On this page, you'll learn about how to [manage custom roles in your project](#manage-custom-roles), the types of privileges you can assign, and how to [assign the roles](#assign-custom-roles) that you create.
 
 ::::{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` 
 ::::
 
 :::{{admonition}} Custom roles in {{stack}}

reference/glossary/index.md

@@ -162,8 +162,11 @@
 $$$glossary-ccs$$$ {{ccs}} (CCS)
 :   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).
+
 $$$CRD$$$CRD
 :   [Custom resource definition](https://kubernetes.io/docs/reference/glossary/?fundamental=true#term-CustomResourceDefinition). {{eck}} extends the Kubernetes API with CRDs to allow users to deploy and manage Elasticsearch, Kibana, APM Server, Enterprise Search, Beats, Elastic Agent, Elastic Maps Server, and Logstash resources just as they would do with built-in Kubernetes resources.
 
 $$$glossary-custom-rule$$$ custom rule
 :   A set of conditions and actions that change the behavior of {{anomaly-jobs}}. You can also use filters to further limit the scope of the rules. See [Custom rules](/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md#ml-ad-rules). {{kib}} refers to custom rules as job rules.
@@ -494,8 +497,11 @@
 :   Source [index](/reference/glossary/index.md#glossary-index) for [{{ccr}}](/reference/glossary/index.md#glossary-ccr). A leader index exists on a [remote cluster](/reference/glossary/index.md#glossary-remote-cluster) and is replicated to [follower indices](/reference/glossary/index.md#glossary-follower-index). See [{{ccr-cap}}](/deploy-manage/tools/cross-cluster-replication.md).
 
 $$$glossary-lens$$$ Lens
 :   Enables you to build visualizations by dragging and dropping data fields. Lens makes makes smart visualization suggestions for your data, allowing you to switch between visualization types. See [Lens](/explore-analyze/dashboards.md).
 
+$$$glossary-linked-project$$$ linked project
+:   An {{serverless-full}} project that is linked to an [origin project](/reference/glossary/index.md#glossary-origin-project). See [{{cps-cap}}](/explore-analyze/cross-project-search.md).
+
 $$$glossary-local-cluster$$$ local cluster
 :   [Cluster](/reference/glossary/index.md#glossary-cluster) that pulls data from a [remote cluster](/reference/glossary/index.md#glossary-remote-cluster) in [{{ccs}}](/reference/glossary/index.md#glossary-ccs) or [{{ccr}}](/reference/glossary/index.md#glossary-ccr). See [Remote clusters](/deploy-manage/remote-clusters/remote-clusters-self-managed.md).
 
@@ -568,6 +574,9 @@
 $$$Operator$$$operator
 :   A design pattern in Kubernetes for [managing custom resources](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/). {{eck}} implements the operator pattern to manage Elasticsearch, Kibana and APM Server resources on Kubernetes.
 
+$$$glossary-origin-project$$$ origin project
+:   In a {{cps}}, the base {{serverless-full}} project where you link projects and run searches. See [{{cps-cap}}](/explore-analyze/cross-project-search.md).
+
 $$$glossary-output-plugin$$$ output plugin
 :   A {{ls}} [plugin](/reference/glossary/index.md#glossary-plugin) that writes [event](/reference/glossary/index.md#glossary-event) data to a specific destination. Outputs are the final stage in the event [pipeline](/reference/glossary/index.md#glossary-pipeline). Popular output plugins include elasticsearch, file, graphite, and statsd.
 
@@ -748,7 +757,7 @@
 ## T [t-glos]
 
 $$$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).
 
 $$$glossary-term-join$$$ term join
 :   A shared key that combines vector features with the results of an {{es}} terms aggregation. Term joins augment vector features with properties for data-driven styling and rich tooltip content in maps.