diff --git a/solutions/images/security-attack-discovery-settings.png b/solutions/images/security-attack-discovery-settings.png
index 2598eeb935..36365be69a 100644
Binary files a/solutions/images/security-attack-discovery-settings.png and b/solutions/images/security-attack-discovery-settings.png differ
diff --git a/solutions/images/security-attck-disc-example-disc.png b/solutions/images/security-attck-disc-example-disc.png
index f36bf0424a..ea2121799e 100644
Binary files a/solutions/images/security-attck-disc-example-disc.png and b/solutions/images/security-attck-disc-example-disc.png differ
diff --git a/solutions/images/security-attck-disc-select-model-empty.png b/solutions/images/security-attck-disc-select-model-empty.png
index 282fead5df..6e241c5609 100644
Binary files a/solutions/images/security-attck-disc-select-model-empty.png and b/solutions/images/security-attck-disc-select-model-empty.png differ
diff --git a/solutions/security/ai/attack-discovery.md b/solutions/security/ai/attack-discovery.md
index e9fe4844ad..a0c6962c6e 100644
--- a/solutions/security/ai/attack-discovery.md
+++ b/solutions/security/ai/attack-discovery.md
@@ -3,9 +3,9 @@ mapped_pages:
   - https://www.elastic.co/guide/en/security/current/attack-discovery.html
   - https://www.elastic.co/guide/en/serverless/current/attack-discovery.html
 applies_to:
-  stack: preview
+  stack: ga
   serverless:
-    security: preview
+    security: ga
 products:
   - id: security
   - id: cloud-serverless
@@ -20,22 +20,26 @@ For a demo, refer to the following video (click to view).
 [![Attack Discovery video](https://play.vidyard.com/eT92arEbpRddmSM4JeyzdX.jpg)](https://videos.elastic.co/watch/eT92arEbpRddmSM4JeyzdX?)
 
 
-This page describes:
-
-* [How to generate discoveries](/solutions/security/ai/attack-discovery.md#attack-discovery-generate-discoveries)
-* [What information each discovery includes](/solutions/security/ai/attack-discovery.md#attack-discovery-what-info)
-* [How you can interact with discoveries to enhance {{elastic-sec}} workflows](/solutions/security/ai/attack-discovery.md#attack-discovery-workflows)
-
-
 ## Role-based access control (RBAC) for Attack Discovery [attack-discovery-rbac]
 
 You need the `Attack Discovery: All` privilege to use Attack Discovery.
 
 ![attack-discovery-rbac](/solutions/images/security-attck-disc-rbac.png)
 
+{applies_to}`stack: ga 9.1` Your role must also have the following privileges:
+
+| Action | Indices | {{es}} privileges |
+|---------|---------|--------------------------|
+| Read Attack Discovery alerts | - `.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.internal.alerts-security.attack.discovery.alerts-<space-id>`<br> - `.adhoc.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.internal.adhoc.alerts-security.attack.discovery.alerts-<space-id>`| `read` and `view_index_metadata` |
+| Read and modify Attack Discovery alerts. This includes:<br>- Generating discovery alerts manually<br>- Generating discovery alerts using schedules<br>- Sharing manually created alerts with other users<br>- Updating a discovery's status |- `.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.internal.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.adhoc.alerts-security.attack.discovery.alerts-<space-id>`<br>- `.internal.adhoc.alerts-security.attack.discovery.alerts-<space-id>`| `read`, `view_index_metadata`, `write`, and `maintenance`|
+
 ## Set up Attack Discovery
 
-By default, Attack Discovery analyzes up to 100 alerts from the last 24 hours, but you can customize how many and which alerts it analyzes using the settings menu. To open it, click the gear icon next to the **Generate** button.
+By default, Attack Discovery analyzes up to 100 alerts from the last 24 hours, but you can customize how many and which alerts it analyzes using the settings menu. To open it, click the settings icon next to the **Run** button.
+
+:::{note}
+In {{stack}} 9.0.0 and earlier, the **Run** button is called **Generate**.
+:::
 
 ::::{image} /solutions/images/security-attack-discovery-settings.png
 :alt: Attack Discovery's settings menu
@@ -47,19 +51,21 @@ You can select which alerts Attack Discovery will process by filtering based on
 :::{admonition} How to add non-ECS fields to Attack Discovery
 Attack Discovery is designed for use with alerts based on data that complies with ECS, and by default only analyses ECS-compliant fields. However, you can enable Attack Discovery to review additional fields by following these steps:
 
-1.  Select an alert with some of the non-ECS fields you want to analyze, and go to its details flyout. From here, use the **Chat** button to open AI Assistant.
+1.  Select an alert with some of the non-ECS fields you want to analyze, and go to its details flyout. From here, use the **Ask AI Assistant** button to open AI Assistant.
 2.  At the bottom of the chat window, the alert's information appears. Click **Edit** to open the anonymization window to this alert's fields.
 3.  Search for and select the non-ECS fields you want Attack Discovery to analyze. Set them to **Allowed**.
 
 The selected fields can now be analyzed the next time you run Attack Discovery.
 :::
 
-## Generate discoveries [attack-discovery-generate-discoveries]
+## Generate discoveries manually[attack-discovery-generate-discoveries]
 
 You’ll need to select an LLM connector before you can analyze alerts. Attack Discovery uses the same LLM connectors as [AI Assistant](/solutions/security/ai/ai-assistant.md). To get started:
 
 1. Click the **Attack Discovery** page from {{elastic-sec}}'s navigation menu.
-2. Select an existing connector from the dropdown menu, or add a new one.
+2. Do one of the following:
+   - {applies_to}`stack: ga 9.1` Click the settings icon next to the **Run** button, then in the settings menu, select an existing connector from the dropdown menu, or add a new one.
+   - {applies_to}`stack: removed 9.1` Select an existing connector from the dropdown menu, or add a new one.
 
    :::{admonition} Recommended models
    While Attack Discovery is compatible with many different models, refer to the [Large language model performance matrix](/solutions/security/ai/large-language-model-performance-matrix.md) to see which models perform best.
@@ -71,9 +77,11 @@ You’ll need to select an LLM connector before you can analyze alerts. Attack D
     :alt: attck disc select model empty
     :::
 
-3. Once you’ve selected a connector, click **Generate** to start the analysis.
-
-It may take from a few seconds up to several minutes to generate discoveries, depending on the number of alerts and the model you selected. Once the analysis is complete, any threats it identifies will appear as discoveries. Click each one’s title to expand or collapse it. Click **Generate** at any time to start the Attack Discovery process again with the selected alerts.
+3. Once you’ve selected a connector, do one of the following to start the analysis:
+   - {applies_to}`stack: ga 9.1` Click **Save and run**.
+   - {applies_to}`stack: removed 9.1` Click **Generate**.
+   
+It may take from a few seconds up to several minutes to generate discoveries, depending on the number of alerts and the model you selected. Once the analysis is complete, any threats it identifies will appear as discoveries. Click each one’s title to expand or collapse it. Click **Run** at any time to start the Attack Discovery process again with the selected alerts.
 
 ::::{important}
 Attack Discovery uses the same data anonymization settings as [Elastic AI Assistant](/solutions/security/ai/ai-assistant.md). To configure which alert fields are sent to the LLM and which of those fields are obfuscated, use the Elastic AI Assistant settings. Consider the privacy policies of third-party LLMs before sending them sensitive data.
@@ -106,3 +114,75 @@ There are several ways you can incorporate discoveries into your {{elastic-sec}}
 :::{image} /solutions/images/security-add-discovery-to-assistant.gif
 :alt: Attack Discovery view in AI Assistant
 :::
+
+## Schedule discoveries
+
+```yaml {applies_to}
+stack: ga 9.1
+```
+
+You can define recurring schedules (for example, daily or weekly) to automatically generate attack discoveries without needing manual runs. For example, you can generate discoveries every 24 hours and send a Slack notification to your SecOps channel if discoveries are found. Notifications are sent using configured [connectors](/deploy-manage/manage-connectors.md), such as Slack or email, and you can customize the notification content to tailor alert context to your needs.
+
+:::{note}
+You can still generate discoveries manually at any time, regardless of an active schedule.
+:::
+
+To create a new schedule:
+
+1. In the top-right corner, select **Schedule**.
+2. In the **Attack discovery schedule** flyout, select **Create new schedule**.
+3. Enter a name for the new schedule.
+4. Select the LLM connector to use for generating discoveries, or add a new one.
+5. Use the KQL query bar, time filter, and alerts slider to customize the set of alerts that will be analyzed.
+6. Define the schedule's frequency (for example, every 24 hours).
+7. Optionally, select the [connectors](/deploy-manage/manage-connectors.md) to use for receiving notifications, and define their actions.
+8. Click **Create & enable schedule**.
+
+After creating new schedules, you can view their status, modify them or delete them from the **Attack discovery schedule** flyout.
+
+:::{tip}
+Scheduled discoveries are shown with a **Scheduled Attack discovery** icon ({icon}`calendar`). Click the icon to view the schedule that created it.
+:::
+
+## View saved discoveries
+
+```yaml {applies_to}
+stack: ga 9.1
+```
+
+Attack discoveries are automatically saved on the **Attack Discovery** page each time you generate them. Once saved, discoveries remain available for later review, reporting, and tracking over time. This allows you to revisit discoveries to monitor trends, maintain audit trails, and support investigations as your environment evolves.
+
+### Change a discovery's status
+
+You can set a discovery's status to indicate that it's under active investigation or that it's been resolved. To do this, click **Take action**, then select **Mark as acknowledged** or **Mark as closed**.
+
+You can choose to change the status of only the discovery, or of both the discovery and the alerts associated with it.
+
+### Share attack discoveries
+
+By default, scheduled discoveries are shared with all users in a {{kib}} space.
+
+Manually generated discoveries are private by default. To share them, change **Not shared** to **Shared** next to the discovery's name.
+
+:::{note}
+Once a discovery is shared, its visibility cannot be changed.
+:::
+
+### Take bulk actions
+
+You can take bulk actions on multiple discoveries, such as bulk-changing their status or adding them to a case. To do this, select the checkboxes next to each discovery, then click **Selected *x* Attack discoveries** and choose the action you want to take.
+
+### Search and filter saved discoveries
+
+You can search and filter saved discoveries to help locate relevant findings.
+
+* Use the search box to perform full-text searches across your generated discoveries.
+
+* **Visibility**: Use this filter to, for example, show only shared discoveries.
+
+* **Status**: Filter discoveries by their current status.
+
+* **Connector**: Filter discoveries by connector name. Connectors that are deleted after discoveries have been generated are shown with a **Deleted** tag.
+
+* Time filter: Adjust the time filter to view discoveries generated within a specific timeframe.
+