ml reqs

Author: natasha-moore-elastic

raw-migrated-files/docs-content/serverless/security-ml-requirements.md

@@ -290,7 +290,6 @@ toc:
       - file: docs-content/serverless/security-llm-connector-guides.md
       - file: docs-content/serverless/security-llm-performance-matrix.md
       - file: docs-content/serverless/security-machine-learning.md
-      - file: docs-content/serverless/security-ml-requirements.md
       - file: docs-content/serverless/security-osquery-placeholder-fields.md
       - file: docs-content/serverless/security-osquery-response-action.md
       - file: docs-content/serverless/security-overview-dashboard.md

raw-migrated-files/toc.yml

@@ -6,14 +6,7 @@ mapped_urls:
 
 # Machine learning job and rule requirements
 
-% What needs to be done: Align serverless/stateful
-
-% Use migrated content from existing pages that map to this page:
-
-% - [x] ./raw-migrated-files/security-docs/security/ml-requirements.md
-% - [ ] ./raw-migrated-files/docs-content/serverless/security-ml-requirements.md
-
-To run and create {{ml}} jobs and rules, you need all of these:
+To run and create {{ml}} jobs and rules in serverless, you need the appropriate [user role](/deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles). In {{stack}}, you need all of these:
 
 * The [appropriate license](https://www.elastic.co/subscriptions)
 * There must be at least one {{ml}} node in your cluster
@@ -26,7 +19,7 @@ Additionally, to configure [alert suppression](/solutions/security/detect-and-al
 For more information, go to [Set up {{ml-features}}](/explore-analyze/machine-learning/setting-up-machine-learning.md).
 
 ::::{important} 
-The `machine_learning_admin` and `machine_learning_user` built-in roles give access to the results of *all* {{anomaly-jobs}}, irrespective of whether the user has access to the source indices. Likewise, a user who has full or read-only access to {{ml-features}} within a given {{kib}} space can view the results of *all* {{anomaly-jobs}} that are visible in that space. You must carefully consider who is given these roles and feature privileges; {{anomaly-job}} results may propagate field values that contain sensitive information from the source indices to the results.
+Some roles (for example, in {{stack}}, the `machine_learning_admin` and `machine_learning_user` built-in roles) give access to the results of *all* {{anomaly-jobs}}, irrespective of whether the user has access to the source indices. Likewise, a user who has full or read-only access to {{ml-features}} within a given {{kib}} space can view the results of *all* {{anomaly-jobs}} that are visible in that space. You must carefully consider who is given these roles and feature privileges; {{anomaly-job}} results may propagate field values that contain sensitive information from the source indices to the results.
 
 ::::