Skip to content

Commit 309338a

Browse files
docs: update Slack AI agent OAuth default to enabled
1 parent 7159d45 commit 309338a

1 file changed

Lines changed: 10 additions & 4 deletions

File tree

references/integrations/slack-integration.mdx

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,18 +40,24 @@ For details on Slack channel limitations and multi-agent support, see [Slack cha
4040

4141
#### User attribution and OAuth
4242

43-
By default, all AI agent conversations in Slack are attributed to the user who installed the Slack app (or created the agent). This means every Slack user's questions will appear as if they came from that single user, and all queries will run with that user's permissions.
43+
New Slack installations require OAuth for AI agents by default. Each Slack user must authenticate with Lightdash before using an AI agent, and queries respect that user's own permissions and [user attributes](/guides/ai-agents/data-access#user-attributes-and-permissions).
4444

45-
To have each Slack user properly identified and use their own permissions, enable the **AI Agents OAuth requirement** toggle in these settings. When enabled:
45+
When the **AI Agents OAuth requirement** toggle is enabled:
4646

4747
- Each Slack user must authenticate with Lightdash before using the AI agent
4848
- Conversations are attributed to the individual user asking the question
4949
- Queries respect each user's own [user attributes and permissions](/guides/ai-agents/data-access#user-attributes-and-permissions)
5050

51+
When the toggle is disabled, all AI agent conversations are attributed to the user who installed the Slack app (or created the agent). Every Slack user's questions appear as if they came from that single user, and all queries run with that user's permissions.
52+
5153
<Tip>
52-
We recommend enabling OAuth if your organization uses row-level or column-level security through user attributes, or if you need an audit trail of which users are asking which questions.
54+
We strongly recommend keeping OAuth enabled if your organization uses row-level or column-level security through user attributes, or if you need an audit trail of which users are asking which questions.
5355
</Tip>
5456

57+
<Note>
58+
Slack installations created before this default change keep their existing setting. Admins can toggle it on from the Slack integration settings page at any time.
59+
</Note>
60+
5561
## Using Lightdash in private channels
5662

5763
Lightdash supports private Slack channels, but because Slack doesn't allow apps to see private channels by default, you'll need to manually add the Lightdash app to your private channel first.
@@ -138,6 +144,6 @@ The Slack integration is also used by AI analyst agents to chat with your data a
138144
To trigger AI responses, mention the Lightdash app in your message. There's only one Lightdash Slack app name to mention - you don't need to specify a particular agent. Lightdash automatically routes your question to the most appropriate agent. If it's unclear which agent should respond, you'll be prompted to choose.
139145

140146
<Note>
141-
By default, all Slack AI agent conversations are attributed to the user who installed the Slack app. To have conversations attributed to individual Slack users (and respect their data permissions), enable the **AI Agents OAuth requirement** in your [Slack integration settings](#ai-agents-configuration).
147+
New Slack installations require OAuth for AI agents by default, so each Slack user authenticates with Lightdash and queries run with their own permissions. If the **AI Agents OAuth requirement** is disabled in your [Slack integration settings](#ai-agents-configuration), all conversations are attributed to the user who installed the Slack app instead.
142148
</Note>
143149

0 commit comments

Comments
 (0)