Add data scope and audit trail info to Slack security docs (#1269)

This PR adds important security information to the Slack integration
documentation based on common questions from users.

## Changes Made

**Added Data Scope and Context section:**
- Explains that when Codegen is mentioned inside a thread, it pulls
context from the entire thread (messages and media)
- Clarifies that when mentioned outside a thread, it only sees the
specific message

**Added Audit Trail section:**
- Documents that administrators can access comprehensive audit logs via
the Recents page
- Mentions filtering capabilities by integration, user, and other
parameters

## Why This Matters

These are common security questions that users ask about the Slack
integration. Having this information readily available in the docs will:
- Reduce support burden by providing self-service answers
- Increase transparency about data handling
- Help administrators understand audit capabilities

The information is placed in the existing "Data Privacy and Security"
section of the Slack integration docs for easy discoverability.

---

[💻 View my work](https://codegen.com/agent/trace/96636) • 👤 Initiated by
`Jay Hack` • 💬 Initiated in
[#customer-requests](https://thecodegen.slack.com/archives/C07KR277H5H/p1758221502180369?thread_ts=1758221460.261039&cid=C07KR277H5H)
• [About Codegen](https://codegen.com)
[⛔ Remove Codegen from
PR](https://codegen.com/agent/trace/96636/remove-from-pr) • [🚫 Ban
action checks](https://codegen.com/agent/trace/96636/ban)

Co-authored-by: codegen-sh[bot] <131295404+codegen-sh[bot]@users.noreply.github.com>
Co-authored-by: jay <[email protected]>

Author: codegen-sh[bot]

docs/integrations/slack.mdx

@@ -118,10 +118,19 @@ The Codegen Slack integration requires the following permissions to function eff
 - **Data Retention:** Outside of the LLM API interactions, message content is retained by Codegen solely for the purpose of displaying it within the Codegen user interface.
 - **Metadata from Private Channels:** When messages from private Slack channels are processed, Codegen does not expose private metadata, such as the original author's name or username, in the Codegen web app. Private channel names are anonymized and displayed as "Private channel" to non-members.
 
+**Data Scope and Context:**
+
+- **Thread Context:** When Codegen is mentioned inside a thread, it will pull context from the entire thread, including the messages sent and media shared within that thread.
+- **Single Message Context:** When Codegen is mentioned outside of a thread, it will only be scoped to the specific message in which it is mentioned.
+
 **User Permissions and Access Control:**
 
 Codegen's actions on connected repositories are governed by the permissions of the user who initiated the interaction via Slack. The bot itself does not have independent permissions to repositories. Access to repositories and the ability to trigger actions are determined by the Codegen user's authenticated account and their associated repository permissions. We recommend configuring channel access carefully during installation to ensure the Codegen integration for Slack is only present in channels where its use is appropriate.
 
+**Audit Trail:**
+
+Administrators can access a comprehensive audit trail through the [Recents page](https://codegen.com/recents) in the Codegen web app. This provides detailed logs of when and by whom Codegen was invoked in Slack, with filtering capabilities by integration, user, and other parameters.
+
 **Privacy Policy:**
 
 For complete details on how we collect, use, and protect your data, please review our [Privacy Policy](https://www.codegen.com/privacy-policy).