[ENG-895] feat: update Slack App documentation

ai/overview.md

@@ -33,6 +33,7 @@ Every entry point below delivers this same context - they differ in where you ar
 | [MCP Server](mcp-server.md)                                  | Any MCP-capable agent             | Agents querying runs, tests, and analytics on demand; autonomous troubleshooting |
 | [IDE Extension](ide-extension.md)                            | VS Code, Cursor, compatible forks | Debugging CI failures without leaving the editor                                 |
 | [Fix with AI](overview.md#fix-with-ai-from-the-dashboard)    | Currents dashboard                | Handing a failure to an agent while triaging a run                               |
+| [Slack Fix with AI](../resources/integrations/slack/slack-app.md#fix-with-ai) | Slack | Handing a failed-test notification to an agent from a team channel |
 | [Playwright Skill](agent-skill-playwright-best-practices.md) | Claude Code, Cursor, other agents | Teaching agents how to write and fix Playwright tests correctly                  |
 | [n8n](../resources/integrations/n8n.md)                      | n8n workflows                     | Automated triage, notifications, and agent pipelines without code                |
 
@@ -84,6 +85,10 @@ You can copy the prompt to your clipboard for any agent, or open it directly in
 
 This is the bridge from investigation to action: whoever is looking at the failing run - not necessarily the person with the repo open - can package the failure with its full context and route it to an agent in one click.
 
+### Fix with AI from Slack
+
+Failed-test notifications from the [Slack App](../resources/integrations/slack/slack-app.md#fix-with-ai) include a **Fix with AI** button. The modal can open the failure in Cursor or GitHub Copilot, provide a copyable prompt for Claude, Codex, Zed, Conductor, and other tools, and link to the Currents MCP installation. This lets anyone monitoring a team channel route a failure to an agent without first opening the Currents dashboard.
+
 ### Playwright Skill
 
 Context tells an agent _what_ failed; the [Playwright Best Practices skill](agent-skill-playwright-best-practices.md) tells it _how_ to fix it well. It's an [Agent Skill](https://agentskills.io/home) - an open standard supported by Claude Code, Cursor, VS Code, and others - that packages expert Playwright knowledge: locator strategy, web-first assertions, debugging flaky tests, CI configuration, and more.
@@ -106,12 +111,6 @@ The [n8n integration](../resources/integrations/n8n.md) connects Currents to mor
 
 Combined with [HTTP webhooks](../resources/integrations/http-webhooks.md) as a trigger, this covers the fully autonomous end of the spectrum - no editor, no dashboard, just test results flowing into whatever process you define.
 
-## Coming up
-
-### Slack
-
-**Fix with AI** is coming to the [Slack integration](../resources/integrations/slack/): failed-test notifications will include a Fix with AI button that opens one-click deep links to AI coding tools, plus a copyable prompt for everything else - prefilled with the same enriched failure context and MCP identifiers as the dashboard and IDE actions. A failure lands in your team channel, and anyone in the thread can route it to an agent without opening the dashboard first.
-
 ## Combining entry points
 
 These methods compose - most teams end up using several:

dashboard/automated-reports.md

@@ -68,8 +68,27 @@ Configure the settings and enable the automated report:
 
 9. Use **Preview** to examine and change the report settings.
 
+### Send automated reports to Slack (Slack App)
+
+Projects with the [Slack App](../resources/integrations/slack/slack-app.md) connected at the organization level can deliver the same scheduled report to Slack channels.
+
+On the report customization page:
+
+1. Enable the report and configure label, filters, lookback period, and schedule as for email.
+2. In the report **Slack** settings, enable **Send to Slack**.
+3. Select the Slack channel or channels that should receive the report. The Currents app must be able to post in each channel (invite the app to private channels if needed).
+4. Save the report. Email recipients and Slack channels can be used together or independently.
+
+At the scheduled time, Currents posts a Block Kit summary to each selected channel, with links to the full report in the dashboard. Message content matches the report’s filters and period; it is a channel-friendly summary rather than a copy of the HTML email.
+
+For prerequisites, channel selection, and troubleshooting, see [Automated Reports to Slack](../resources/integrations/slack/slack-app.md#automated-reports-to-slack).
+
 ### Forward automated reports email to Slack
 
+{% hint style="info" %}
+**Recommendation:** When the organization uses the Currents Slack App, prefer [native Slack delivery](#send-automated-reports-to-slack-slack-app) on the report instead of forwarding email. Native delivery posts structured Block Kit messages and does not depend on Slack inbound email addresses.
+{% endhint %}
+
 Slack currently allows receiving emails in a Slack channel or private message.
 
 Slack generates an email where the automated reports will be sent and that must be registered in the dashboard. Slack then receives the email and forwards the email to the previously setup channel.

guides/currents-actions/lifecycle-notifications.md

@@ -23,7 +23,7 @@ Enabling Slack notifications requires two steps:
 1. **Connect Slack to the organization** following the [#installation](../../resources/integrations/slack/slack-app.md#installation "mention").
 
 {% hint style="info" %}
-Note that this OAuth flow requires an organization administrator.
+A **Currents organization administrator** must connect, re-authenticate, or disconnect the integration. A **Slack administrator** must authorize the app; the exact required Slack role depends on whether the account uses a single workspace or Enterprise Grid.
 {% endhint %}
 
 <figure><img src="../../.gitbook/assets/image (48).png" alt=""><figcaption><p>Missing Slack App installation</p></figcaption></figure>
@@ -37,7 +37,7 @@ Connecting Slack under Integrations alone does not enable notifications — they
 
 <figure><img src="../../.gitbook/assets/image (59).png" alt=""><figcaption><p>Slack channel configuration</p></figcaption></figure>
 
-Once Slack is connected, anyone with **Actions Admin** access can configure the channel and events. If the Slack option is unavailable, an organization administrator must complete the Integrations setup first.
+Once Slack is connected, anyone with **Actions Admin** access can configure the channel and events. If the Slack option is unavailable, a Currents organization administrator must complete the Integrations setup first.
 
 #### Email
 

resources/data-privacy/access-to-customer-data.md

@@ -52,4 +52,5 @@ We collect diverse data from our users' test suites, which are strictly limited
 * **GitHub**: No access to data or repos source code; we post comments and status check updates for Pull Requests. The integration application is listed here: [https://github.com/apps/currents-bot](https://github.com/apps/currents-bot), and the list of permissions appears as part of the setup.
 * **GitLab**: We list repositories and projects, refresh oAuth tokens, post notes and status check updates to Merge Requests, fetching Merge Request details.
 * **BitBucket**: No access to data; we only post status check updates for Pull Requests.
-* **Microsoft Teams, Slack**: No access to data, just posting messages within the restrictions of the platform's rules.
+* **Microsoft Teams**: Currents posts messages within the restrictions of the platform's rules.
+* **Slack**: The Slack App lists accessible channels; reads workspace, user, email, and user-group metadata; posts messages and thread replies; sends direct installation and re-authentication messages; and processes supported Slack interactions and message metadata. Access is limited by the OAuth permissions approved during installation and Slack channel-membership rules.

resources/integrations/slack/README.md

@@ -1,33 +1,40 @@
 ---
 description: >-
-  Integrating Slack with Currents dashboard for Playwright and Cypress test
-  notifications
+  Integrating Slack with Currents dashboard for test notifications
 icon: slack
 ---
 
 # Slack
 
-Currents integration with Slack allows posting test results of your Playwright or Cypress tests directly into Slack channels, helping your team stay informed about test outcomes without leaving Slack.
+Currents integration with Slack allows posting test results directly into Slack channels, helping teams stay informed about test outcomes without leaving Slack.
 
 There are two versions of Slack integration available:
 
 {% hint style="info" %}
-**Recommendation:** We recommend using the Slack App integration due to its advanced features and improved security model.
+**Recommendation:** Currents recommends using the Slack App integration due to its advanced features and improved security model.
 {% endhint %}
 
 ## [Slack App](slack-app.md) Integration (Recommended)
 
 The Slack App integration provides a rich, feature-complete experience for test notifications:
 
 * ✅ Organization-level installation with per-project configuration
-* ✅ Multiple destinations (up to 10 channels per project)
+* ✅ Multiple destinations (the dashboard shows the organization's limit; the default is 10)
 * ✅ Run-level notifications with thread-based grouping
-* ✅ Individual test failure notifications
+* ✅ Individual failed or flaky test notifications
+* ✅ Fix with AI from failed-test messages
+* ✅ Run attachment colors for in-progress, success, and error states
+* ✅ Live updates to the groups table on threaded run notifications
 * ✅ Advanced filtering by tags, branches, and commit messages
 * ✅ Annotation-based mentions (users, groups, emails)
 * ✅ UI-based mention rules configuration
+* ✅ Scheduled [Automated Reports](../../../dashboard/automated-reports.md) to Slack channels (Block Kit summaries with dashboard links)
 * ✅ Improved security with OAuth 2.0
 
+The Slack App also delivers independently configured [Action lifecycle notifications](../../../guides/currents-actions/lifecycle-notifications.md) for actions that are created, disabled, re-enabled, archived, expiring, or expired. Connecting Slack under **Integrations** does not enable these notifications; Action notifications are configured under **Actions > Settings**.
+
+Scheduled automated reports are configured per report on the project **Reports** page; see [Automated Reports to Slack](slack-app.md#automated-reports-to-slack).
+
 ## [Slack Webhook](slack-webhook.md) Integration (Legacy)
 
 The webhook-based integration provides basic notification functionality: