diff --git a/solutions/security/advanced-entity-analytics.md b/solutions/security/advanced-entity-analytics.md
index 91bde5b11c..26ae4885fc 100644
--- a/solutions/security/advanced-entity-analytics.md
+++ b/solutions/security/advanced-entity-analytics.md
@@ -15,7 +15,9 @@ products:
 
 Advanced Entity Analytics generates a set of threat detection and risk analytics that allows you to expedite alert triage and hunt for new threats from within an entity’s environment. This feature combines the power of the SIEM detection engine and Elastic’s {{ml}} capabilities to identify unusual user behaviors and generate comprehensive risk analytics for hosts, users, and services.
 
-Advanced Entity Analytics provides two key capabilities:
+Advanced Entity Analytics provides the following key capabilities:
 
-* [Entity risk scoring](advanced-entity-analytics/entity-risk-scoring.md)
-* [Advanced behavioral detections](advanced-entity-analytics/advanced-behavioral-detections.md)
+* [](advanced-entity-analytics/entity-risk-scoring.md)
+* [](advanced-entity-analytics/advanced-behavioral-detections.md)
+* {applies_to}`stack: preview 9.1` {applies_to}`serverless: unavailable`	
+ [](/solutions/security/advanced-entity-analytics/privileged-user-monitoring.md)
diff --git a/solutions/security/advanced-entity-analytics/asset-criticality.md b/solutions/security/advanced-entity-analytics/asset-criticality.md
index 8d35179eff..e2478ef2d6 100644
--- a/solutions/security/advanced-entity-analytics/asset-criticality.md
+++ b/solutions/security/advanced-entity-analytics/asset-criticality.md
@@ -66,7 +66,10 @@ You can view, assign, change, or unassign asset criticality from the following p
     :::
 
 
-If you have enabled the [entity store](entity-store.md), you can also view asset criticality assignments in the [**Entities** section](../dashboards/entity-analytics-dashboard.md#entity-entities) of the Entity Analytics dashboard:
+If you have enabled the [entity store](entity-store.md), you can also view asset criticality assignments in the **Entities** section on the following pages:
+
+* {applies_to}`stack: ga 9.1` {applies_to}`serverless: unavailable` [Entity analytics](/solutions/security/advanced-entity-analytics/overview.md)
+* [Entity analytics dashboard](/solutions/security/dashboards/entity-analytics-dashboard.md)
 
 :::{image} /solutions/images/security-entities-section.png
 :alt: Entities section
diff --git a/solutions/security/advanced-entity-analytics/entity-store.md b/solutions/security/advanced-entity-analytics/entity-store.md
index 35c84824d7..8044ef5ca5 100644
--- a/solutions/security/advanced-entity-analytics/entity-store.md
+++ b/solutions/security/advanced-entity-analytics/entity-store.md
@@ -42,8 +42,10 @@ To enable the entity store:
 1. Find **Entity Store** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. On the **Entity Store** page, turn the toggle on.
 
-Once you enable the entity store, the Entity Analytics dashboard displays the [**Entities**](../dashboards/entity-analytics-dashboard.md#entity-entities) section.
+Once you enable the entity store, the **Entities** section appears on the following pages:
 
+* {applies_to}`stack: ga 9.1` {applies_to}`serverless: unavailable` [Entity analytics](/solutions/security/advanced-entity-analytics/overview.md)
+* [Entity analytics dashboard](/solutions/security/dashboards/entity-analytics-dashboard.md)
 
 ## Clear entity store data [clear-entity-store]
 
diff --git a/solutions/security/advanced-entity-analytics/monitor-privileged-user-activitites.md b/solutions/security/advanced-entity-analytics/monitor-privileged-user-activitites.md
new file mode 100644
index 0000000000..d9bb30d993
--- /dev/null
+++ b/solutions/security/advanced-entity-analytics/monitor-privileged-user-activitites.md
@@ -0,0 +1,37 @@
+---
+applies_to:
+  stack: preview 9.1
+products:
+  - id: security
+  - id: cloud-serverless
+---
+
+# Monitor privileged user activities
+
+After you [set up privileged user monitoring](/solutions/security/advanced-entity-analytics/privileged-user-monitoring-setup.md), you can start monitoring your privileged users' activity using the different panels on the Privileged user monitoring dashboard.
+
+To get started, find **Privileged user monitoring** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+
+## Risk levels of privileged users
+
+When entity risk scoring is enabled, this panel shows the percentages and numbers of privileged users exhibiting risky behaviors that trigger alerts, grouped by their risk levels. This helps you assess how much risk administrative and other privileged users are contributing to your environment’s overall risk posture.
+
+## Privileged users
+
+This panel represents an inventory of privileged users, sourced from your provided [data sources](/solutions/security/advanced-entity-analytics/privileged-user-monitoring-setup.md#manage-data-sources). It gives a rich catalog of users that may be valuable to investigate, and provides additional information, including user risk scores and asset criticality assignment. This table also serves as a window into the users that are currently being monitored for their privileged status from the configured data sources.
+
+## Top privileged access anomalies
+
+The [Privileged Access Detection](integration-docs://reference/pad.md) package contains multiple {{ml}} jobs that can detect anomalous privileged user activity across various systems, such as Windows, Linux, and Okta system logs. You can install this package directly from the Privileged user monitoring dashboard and access the related {{ml}} jobs for any additional configuration.
+
+Once you install the package, this panel displays a heatmap of the top privileged access anomalies performed by your defined privileged users. You can investigate these anomalies further by reviewing details for individual users or by navigating to the Anomaly Explorer.
+
+## Privileged user activity
+
+This panel contains the following tabs:
+
+* **Granted rights**: Monitor when rights are granted. This helps you detect behavior such as over-provisioning or potential insider threats. It also highlights possible misuse of administrative privileges or violations of least-privilege policies.
+
+* **Account switches**: Track when privileged users switch accounts. This can help you proactively identify potential lateral movement or unauthorized access.
+
+* **Authentications**: Review authentication events for privileged users. Frequent authentication shows how actively these privileges are being used, while repeated failed authentication events can indicate attempted unauthorized access.
diff --git a/solutions/security/advanced-entity-analytics/overview.md b/solutions/security/advanced-entity-analytics/overview.md
new file mode 100644
index 0000000000..870ea6e515
--- /dev/null
+++ b/solutions/security/advanced-entity-analytics/overview.md
@@ -0,0 +1,173 @@
+---
+applies_to:
+  stack: ga 9.1
+products:
+  - id: security
+  - id: cloud-serverless
+---
+
+# Entity analytics overview
+
+The **Entity analytics** page provides a centralized view of emerging insider threats—including host risk, user risk, service risk, and anomalies from within your network. Use it to triage, investigate, and respond to these emerging threats.
+
+To access the page, find **Entity analytics** → **Overview** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+
+:::{admonition} Requirements
+* This feature requires the appropriate [subscription](https://www.elastic.co/pricing) in {{stack}} or [project feature](/deploy-manage/deploy/elastic-cloud/project-settings.md) in {{serverless-short}}.
+
+* To get access to this page, turn on the `securitySolution:enablePrivilegedUserMonitoring` [advanced setting](/solutions/security/get-started/configure-advanced-settings.md#access-privileged-user-monitoring).
+:::
+
+
+The  **Entity analytics** page includes the following sections:
+
+* [Entity KPIs (key performance indicators)](#entity-kpis)
+* [User Risk Scores](#entity-user-risk-scores)
+* [Host Risk Scores](#entity-host-risk-scores)
+* [Service Risk Scores](#service-risk-scores)
+* [Entities](#entity-entities)
+* [Anomalies](#entity-anomalies)
+
+
+## Entity KPIs (key performance indicators) [entity-kpis]
+
+This section displays the total number of critical hosts, critical users, and anomalies. Select a link to jump to the **Hosts** page, **Users** page, or **Anomalies** table.
+
+
+## User Risk Scores [entity-user-risk-scores]
+
+:::{admonition} Requirements
+To display user risk scores, you must [turn on the risk scoring engine](/solutions/security/advanced-entity-analytics/turn-on-risk-scoring-engine.md).
+:::
+
+
+This section displays user risk score data for your environment, including the total number of users, and the five most recently recorded user risk scores, with their associated user names, risk data, and number of detection alerts. User risk scores are [calculated](/solutions/security/advanced-entity-analytics/entity-risk-scoring.md#how-is-risk-score-calculated) using a weighted sum on a scale of 0 (lowest) to 100 (highest).
+
+:::{image} /solutions/images/security-user-score-data.png
+:alt: User risk table
+:screenshot:
+:::
+
+Interact with the table to filter data, view more details, and take action:
+
+* Select the **User risk level** menu to filter the chart by the selected level.
+* Click **View all** to display all user risk information on the **Users** page.
+* Click a user name link to open the entity details flyout.
+* Hover over a user name link to display inline actions: **Add to timeline** ({icon}`timeline`) and **Copy to Clipboard** ({icon}`copy_clipboard`).
+* Click the number link in the **Alerts** column to view the alerts on the **Alerts** page. Hover over the number and select **Investigate in timeline** ({icon}`timeline`) to launch Timeline with a query that includes the associated user name value.
+
+For more information about user risk scores, refer to [](/solutions/security/advanced-entity-analytics/entity-risk-scoring.md).
+
+
+## Host Risk Scores [entity-host-risk-scores]
+
+:::{admonition} Requirements
+To display host risk scores, you must [turn on the risk scoring engine](/solutions/security/advanced-entity-analytics/turn-on-risk-scoring-engine.md).
+:::
+
+
+This section displays host risk score data for your environment, including the total number of hosts, and the five most recently recorded host risk scores, with their associated host names, risk data, and number of detection alerts. Host risk scores are [calculated](/solutions/security/advanced-entity-analytics/entity-risk-scoring.md#how-is-risk-score-calculated) using a weighted sum on a scale of 0 (lowest) to 100 (highest).
+
+:::{image} /solutions/images/security-host-score-data.png
+:alt: Host risk scores table
+:screenshot:
+:::
+
+Interact with the table to filter data, view more details, and take action:
+
+* Select the **Host risk level** menu to filter the chart by the selected level.
+* Click **View all** to display all host risk information on the **Hosts** page.
+* Click a host name link to open the entity details flyout.
+* Hover over a host name link to display inline actions: **Add to timeline** ({icon}`timeline`) and **Copy to Clipboard** ({icon}`copy_clipboard`).
+* Click the number link in the **Alerts** column to view the alerts on the **Alerts** page. Hover over the number and select **Investigate in timeline** ({icon}`timeline`) to launch Timeline with a query that includes the associated host name value.
+
+For more information about host risk scores, refer to [](/solutions/security/advanced-entity-analytics/entity-risk-scoring.md).
+
+
+## Service Risk Scores
+
+:::{admonition} Requirements
+To display service risk scores, you must [turn on the risk scoring engine](/solutions/security/advanced-entity-analytics/turn-on-risk-scoring-engine.md).
+:::
+
+This section displays service risk score data for your environment, including the total number of services, and the five most recently recorded service risk scores, with their associated service names, risk data, and number of detection alerts. Service risk scores are [calculated](/solutions/security/advanced-entity-analytics/entity-risk-scoring.md#how-is-risk-score-calculated) using a weighted sum on a scale of 0 (lowest) to 100 (highest).
+
+:::{image} /solutions/images/security-service-risk-scores.png
+:alt: Service risk scores table
+:screenshot:
+:::
+
+
+Interact with the table to filter data, view more details, and take action:
+
+* Select the **Service risk level** menu to filter the chart by the selected level.
+* Click a service name link to open the service details flyout.
+* Hover over a service name link to display inline actions: **Add to timeline** ({icon}`timeline`) and **Copy to Clipboard** ({icon}`copy_clipboard`).
+* Click the number link in the **Alerts** column to view the alerts on the **Alerts** page. Hover over the number and select **Investigate in timeline** ({icon}`timeline`) to launch Timeline with a query that includes the associated service name value.
+
+For more information about service risk scores, refer to [](/solutions/security/advanced-entity-analytics/entity-risk-scoring.md).
+
+
+## Entities [entity-entities]
+
+
+:::{admonition} Requirements
+To display the **Entities** section, you must [enable the entity store](/solutions/security/advanced-entity-analytics/entity-store.md#enable-entity-store).
+:::
+
+
+This section provides a centralized view of all hosts, users, and services in your environment. It displays entities from the [entity store](/solutions/security/advanced-entity-analytics/entity-store.md), which meet any of the following criteria:
+
+* Have been observed by {{elastic-sec}}
+* Have an asset criticality assignment
+* Have been added to {{elastic-sec}} through an integration, such Active Directory or Okta
+
+:::{note}
+The **Entities** table only shows a subset of the data available for each entity. You can query the `.entities.v1.latest.security_user_<space-id>`, `.entities.v1.latest.security_host_<space-id>`, and `.entities.v1.latest.security_service_<space-id>` indices to see all the fields for each entity in the entity store.
+:::
+
+
+:::{image} /solutions/images/security-entities-section.png
+:alt: Entities section
+:screenshot:
+:::
+
+Entity data from different sources appears in the **Entities** section based on the following timelines:
+
+* When you first enable the entity store, only data stored in the last 24 hours is processed. After that, data is processed continuously.
+* Observed events from the {{elastic-sec}} default data view are processed in near real-time.
+* Entity Analytics data, such as entity risk scores and asset criticality (including bulk asset criticality upload), is also processed in near real-time.
+* The availability of entities extracted from Entity Analytics integrations depends on the specific integration. Refer to [Active Directory Entity Analytics](https://docs.elastic.co/en/integrations/entityanalytics_ad), [Microsoft Entra ID Entity Analytics](https://docs.elastic.co/en/integrations/entityanalytics_entra_id), and [Okta Entity Analytics](https://docs.elastic.co/en/integrations/entityanalytics_okta) for more details.
+
+Interact with the table to filter data and view more details:
+
+* Select the **Risk level** dropdown to filter the table by the selected user, host, or service risk level.
+* Select the **Criticality** dropdown to filter the table by the selected asset criticality level.
+* Select the **Source** dropdown to filter the table by the data source.
+* Click the **View details** icon ({icon}`expand` ) to open the entity details flyout.
+
+
+
+## Anomalies [entity-anomalies]
+
+Anomaly detection jobs identify suspicious or irregular behavior patterns. The **Anomalies** table displays the total number of anomalies identified by these prebuilt {{ml}} jobs (named in the **Anomaly name** column).
+
+:::{admonition} Requirements
+To display anomaly results, you must [install and run](/explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md) one or more [prebuilt anomaly detection jobs](/reference/data-analysis/machine-learning/ootb-ml-jobs-siem.md). You cannot add custom anomaly detection jobs to the **Entity analytics** page.
+:::
+
+
+:::{image} /solutions/images/security-anomalies-table.png
+:alt: Anomalies table
+:screenshot:
+:::
+
+Interact with the table to view more details:
+
+* Click **View all host anomalies** to go to the **Anomalies** table on the **Hosts** page.
+* Click **View all user anomalies** to go to the **Anomalies** table on the **Users** page.
+* Click **View all** to display and manage all machine learning jobs on the **Anomaly Detection Jobs** page.
+
+:::{tip}
+To learn more about {{ml}}, refer to [](/explore-analyze/machine-learning.md)
+:::
\ No newline at end of file
diff --git a/solutions/security/advanced-entity-analytics/privileged-user-monitoring-requirements.md b/solutions/security/advanced-entity-analytics/privileged-user-monitoring-requirements.md
new file mode 100644
index 0000000000..87cc6cd8ac
--- /dev/null
+++ b/solutions/security/advanced-entity-analytics/privileged-user-monitoring-requirements.md
@@ -0,0 +1,31 @@
+---
+applies_to:
+  stack: preview 9.1
+products:
+  - id: security
+  - id: cloud-serverless
+---
+
+# Privileged user monitoring requirements
+
+This page covers the requirements for using the privileged user monitoring feature, as well as its known limitations.
+
+* Privileged user monitoring feature requires the appropriate [subscription](https://www.elastic.co/pricing).
+
+* To enable this feature, turn on the `securitySolution:enablePrivilegedUserMonitoring` [advanced setting](/solutions/security/get-started/configure-advanced-settings.md#access-privileged-user-monitoring).
+
+* To use these features , your role must have certain [privileges](#privmon_privs).
+
+## Privileges [privmon_privs]
+
+| Action | Index Privileges | Kibana Privileges |
+| ------ | ---------------- | ----------------- |
+| Enable the privileged user monitoring feature | N/A | **All** for the **Security** feature |
+| View the Privileged user monitoring dashboard | `Read` for the following indices:<br> - `.entity_analytics.monitoring.users-<space-id>`<br> - `risk-score.risk-score-*`<br> - `.alerts-security.alerts-<space-id>`<br> -  `.ml-anomalies-shared`<br> - Security data view indices | **Read** for the **Security** feature |
+
+## Known limitations
+
+* Currently, none of the privileged user monitoring visualizations support [cross-cluster search](/solutions/search/cross-cluster-search.md) as part of the data that they query from. 
+
+* You can define up to 10,000 privileged users per data source.
+
diff --git a/solutions/security/advanced-entity-analytics/privileged-user-monitoring-setup.md b/solutions/security/advanced-entity-analytics/privileged-user-monitoring-setup.md
new file mode 100644
index 0000000000..9029ba77c2
--- /dev/null
+++ b/solutions/security/advanced-entity-analytics/privileged-user-monitoring-setup.md
@@ -0,0 +1,84 @@
+---
+navigation_title: Set up privileged user monitoring
+applies_to:
+  stack: preview 9.1
+products:
+  - id: security
+  - id: cloud-serverless
+---
+
+# Set up and manage privileged user monitoring
+
+:::{admonition} Requirements
+To use privileged user monitoring, you must:
+
+* Have the appropriate user role or privileges
+* Turn on the required advanced setting
+
+For more information, refer to [Privileged user monitoring requirements](/solutions/security/advanced-entity-analytics/privileged-user-monitoring-requirements.md).
+:::
+
+Before you can start monitoring privileged users, you need to define which users in your environment are considered privileged.
+
+Privileged users typically include accounts with elevated access rights that allow them to configure security settings, manage user permissions, or access sensitive data. 
+
+## Define privileged users
+
+You can define privileged users in the following ways:
+
+* [Select an existing index](#privmon-index) or create a new custom index with privileged user data.
+* [Bulk-upload](#privmon-upload) a list of privileged users using a CSV or TXT file. 
+* Use the Entity analytics APIs to [mark individual users as privileged]({{kib-apis}}/operation/operation-createprivmonuser) or [bulk-upload multiple privileged users]({{kib-apis}}/operation/operation-privmonbulkuploaduserscsv).
+
+To get started, find the **Privileged user monitoring** page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+
+### Select or create an index [privmon-index]
+
+1. On the **Privileged user monitoring** page, click **Index**.
+2. From the **Select index** popup, you can create new or choose existing indices as your data source.
+3. Select **Add privileged users**.
+
+All user names, specified in the `user.name` field in your selected indices, will be defined as privileged users.
+
+### Import a list of privileged users from a text file [privmon-upload]
+
+1. On the **Privileged user monitoring** page, click **File**.
+2. Select or drag and drop the file you want to import. The maximum file size is 1 MB.
+3. Select **Add privileged user**.
+
+The file must contain at least one column, with each user record listed on a separate row:
+
+1. The first column specifies the privileged user's user name.
+2. An optional second column may specify a label, representing the user’s role, group, team, or similar.
+
+File structure example:
+
+```txt
+superadmin
+admin01,Domain Admin
+sec_ops
+jdoe,IT Support
+```
+
+:::{note}
+Any lines that don’t follow the required file structure will be highlighted, and those users won't be added. We recommend that you fix any invalid lines and re-upload the file.
+:::
+
+After setting up your privileged users, you can start [monitoring their activity](/solutions/security/advanced-entity-analytics/monitor-privileged-user-activitites.md) and related insights on the Privileged user monitoring dashboard.
+
+You can update the selected data sources at any time by selecting **Manage data sources**.
+
+## Manage data sources
+
+Use the **Manage data sources** page to update your selected data sources.
+
+You can use multiple data source types, such as an index and a CSV file, at the same time to define privileged users. Users defined through different data source types are monitored together.
+
+On this page, you can:
+
+* View, remove, and change indices after initially defining them.
+* Import a new supported file with a list of privileged users.
+
+   :::{note}
+   Importing a new file will overwrite any users added from a previous file. This doesn't affect users defined through other data source types.
+   :::
\ No newline at end of file
diff --git a/solutions/security/advanced-entity-analytics/privileged-user-monitoring.md b/solutions/security/advanced-entity-analytics/privileged-user-monitoring.md
index 60cafde3b3..72833189c8 100644
--- a/solutions/security/advanced-entity-analytics/privileged-user-monitoring.md
+++ b/solutions/security/advanced-entity-analytics/privileged-user-monitoring.md
@@ -1,8 +1,6 @@
 ---
 applies_to:
   stack: preview 9.1
-  serverless:
-    security: preview 9.1
 products:
   - id: security
   - id: cloud-serverless
@@ -10,4 +8,8 @@ products:
 
 # Privileged user monitoring
 
-This page is a placeholder for future documentation.
+Privileged user monitoring allows you to track the activity of users with elevated permissions, such as system administrators or users with access to sensitive data. These accounts are often targets for attackers who try to gain elevated privileges and access critical systems. To reduce this risk, it’s important to monitor and audit privileged users’ behavior regularly. 
+
+Use privileged user monitoring to proactively identify suspicious activities, such as over-provisioning of rights or malicious insider threats, before they cause damage.
+
+The [Privileged user monitoring dashboard](/solutions/security/advanced-entity-analytics/monitor-privileged-user-activitites.md) gives you a centralized, high-level view of privileged users’ activity. It helps you identify suspicious behavior, prioritize investigations, and quickly access the data you need to respond.
diff --git a/solutions/security/advanced-entity-analytics/view-analyze-risk-score-data.md b/solutions/security/advanced-entity-analytics/view-analyze-risk-score-data.md
index 788e767eab..a29641bd03 100644
--- a/solutions/security/advanced-entity-analytics/view-analyze-risk-score-data.md
+++ b/solutions/security/advanced-entity-analytics/view-analyze-risk-score-data.md
@@ -15,7 +15,7 @@ products:
 
 The {{security-app}} provides several options to monitor the change in the risk posture of hosts and users from your environment. Use the following places in the {{security-app}} to view and analyze risk score data:
 
-* [Entity Analytics dashboard](#entity-analytics-dashboard)
+* [Entity Analytics overview](#entity-analytics-overview)
 * [Alerts page](#alerts-page)
 * [Alert details flyout](#alert-details-flyout)
 * [Hosts and Users pages](#hosts-users-pages)
@@ -28,11 +28,15 @@ We recommend that you prioritize [alert triaging](#alert-triaging) to identify a
 
 
 
-## Entity Analytics dashboard [entity-analytics-dashboard]
+## Entity Analytics overview [entity-analytics-overview]
 
-From the Entity Analytics dashboard, you can access entity key performance indicators (KPIs), risk scores, and levels. You can also click the number link in the **Alerts** column to investigate and analyze the alerts on the Alerts page.
+In the Entity Analytics overview, you can view entity key performance indicators (KPIs), risk scores, and levels. You can also click the number link in the **Alerts** column to investigate and analyze the alerts on the Alerts page.
 
-If you have enabled the [entity store](entity-store.md), the dashboard also displays the [**Entities** section](../dashboards/entity-analytics-dashboard.md#entity-entities), where you can view all hosts, users, and services along with their risk and asset criticality data.
+If you have enabled the [entity store](entity-store.md), you'll also get access to the **Entities** section, where you can view all hosts, users, and services along with their risk and asset criticality data.
+
+Access the Entity Analytics overview from the following pages:
+* {applies_to}`stack: ga 9.1` {applies_to}`serverless: unavailable` [Entity analytics](/solutions/security/advanced-entity-analytics/overview.md) 
+* [Entity analytics dashboard](/solutions/security/dashboards/entity-analytics-dashboard.md)
 
 
 ## Alert triaging [alert-triaging]
diff --git a/solutions/security/advanced-entity-analytics/view-entity-details.md b/solutions/security/advanced-entity-analytics/view-entity-details.md
index 08fac00af9..38da248e91 100644
--- a/solutions/security/advanced-entity-analytics/view-entity-details.md
+++ b/solutions/security/advanced-entity-analytics/view-entity-details.md
@@ -10,7 +10,7 @@ applies_to:
 You can lean more about an entity (host, user, or service) from the entity details flyout, which is available throughout the {{elastic-sec}} app. To access this flyout, click on an entity name in places such as:
 
 * The Alerts table
-* The Entity Analytics dashboard
+* The Entity Analytics overview
 * The **Users** and user details pages
 * The **Hosts** and host details pages
 
diff --git a/solutions/security/get-started/configure-advanced-settings.md b/solutions/security/get-started/configure-advanced-settings.md
index c55aa271e3..7a42054219 100644
--- a/solutions/security/get-started/configure-advanced-settings.md
+++ b/solutions/security/get-started/configure-advanced-settings.md
@@ -13,7 +13,7 @@ products:
 
 # Configure advanced settings [security-advanced-settings]
 
-The advanced settings determine:
+The advanced settings control the behavior of the {{security-app}}, such as:
 
 * Which indices {{elastic-sec}} uses to retrieve data
 * {{ml-cap}} anomaly score display threshold
@@ -212,3 +212,13 @@ To only exclude cold and frozen data from specific rules, add a [Query DSL filte
 ::::{important}
 Even when the `excludedDataTiersForRuleExecution` advanced setting is enabled, indicator match, event correlation, and {{esql}} rules may still fail if a frozen or cold shard that matches the rule’s specified index pattern is unavailable during rule executions. If failures occur, we recommend modifying the rule’s index patterns to only match indices containing hot tier data.
 ::::
+
+
+## Access privileged user monitoring
+```yaml {applies_to}
+stack: preview 9.1
+serverless: unavailable
+```
+
+The `securitySolution:enablePrivilegedUserMonitoring` setting allows you to access the [Entity analytics overview page](/solutions/security/advanced-entity-analytics/overview.md) and the [privileged user monitoring](/solutions/security/advanced-entity-analytics/privileged-user-monitoring.md) feature. This setting is turned off by default.
+
diff --git a/solutions/security/get-started/elastic-security-ui.md b/solutions/security/get-started/elastic-security-ui.md
index 5013cfcf8d..2920425c19 100644
--- a/solutions/security/get-started/elastic-security-ui.md
+++ b/solutions/security/get-started/elastic-security-ui.md
@@ -185,6 +185,23 @@ The Assets section allows you to manage the following features:
 
 * [Cloud security](/solutions/security/cloud.md)
 
+
+### Entity analytics
+```yaml {applies_to}
+stack: preview 9.1
+serverless: unavailable
+```
+
+:::{admonition} Requirements
+To access this section, turn on the `securitySolution:enablePrivilegedUserMonitoring` [advanced setting](/solutions/security/get-started/configure-advanced-settings.md#access-privileged-user-monitoring).
+:::
+
+Expand this section to access the following pages:
+
+- [Entity analytics](/solutions/security/advanced-entity-analytics/overview.md): Access a comprehensive overview of entity risk scores and anomalies identified by prebuilt {{anomaly-jobs}}.
+- [Privileged user monitoring](/solutions/security/advanced-entity-analytics/monitor-privileged-user-activitites.md): Set up your privileged users and monitor their activities to identify suspicious behavior. 
+
+
 ### {{ml-cap}} [security-ui-ml-cap]
 
 Manage {{ml}} jobs and settings. Refer to [{{ml-cap}} docs](/explore-analyze/machine-learning/anomaly-detection.md) for more information.
diff --git a/solutions/toc.yml b/solutions/toc.yml
index a8a3c9b20b..1de366e060 100644
--- a/solutions/toc.yml
+++ b/solutions/toc.yml
@@ -657,6 +657,7 @@ toc:
           - file: security/explore/users-page.md
       - file: security/advanced-entity-analytics.md
         children:
+          - file: security/advanced-entity-analytics/overview.md 
           - file: security/advanced-entity-analytics/entity-risk-scoring.md
             children:
               - file: security/advanced-entity-analytics/entity-risk-scoring-requirements.md
@@ -671,6 +672,10 @@ toc:
               - file: security/advanced-entity-analytics/anomaly-detection.md
               - file: security/advanced-entity-analytics/optimizing-anomaly-results.md
               - file: security/advanced-entity-analytics/behavioral-detection-use-cases.md
-          - hidden: security/advanced-entity-analytics/privileged-user-monitoring.md
+          - file: security/advanced-entity-analytics/privileged-user-monitoring.md
+            children:
+              - file: security/advanced-entity-analytics/privileged-user-monitoring-requirements.md
+              - file: security/advanced-entity-analytics/privileged-user-monitoring-setup.md
+              - file: security/advanced-entity-analytics/monitor-privileged-user-activitites.md
       - file: security/asset-management.md
       - file: security/apis.md
\ No newline at end of file