-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Slack] Allow indexing private channels #8559
Conversation
🔥 Can we just make sure that the auto-join Slack channel does not automatically add private channels 🙏 ? |
Thanks for the check! not sure what you mean? Dust doesn't see private channels it has not been added to by a user of the channel. So it cannot add itself? But I'd be glad if you could review the PR though 😉 🙏 |
72226b1
to
ea592cc
Compare
I meant that in connectors we automatically add Slack channels that match a pattern. We might want to ensure it does not add Private channels automatically. More context here:
|
it can't add private channels this way because it doesn't see them 🙈 This auto add is for channels for which we receive a webhook notification via the "channels_created" webhook; which is unchanged by this PR so no risk there 👍 If the channel creator added the Dust bot when creating the channel, the channel would indeed be added but that's |
if (privateNodes.length > 0) { | ||
const confirmed = await confirm({ | ||
title: "Sensitive data synchronization", | ||
message: `You are synchronizing data from ${privateNodes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we say something like "You are synchronizing data from those private channels:"? I think it may be confusing for people if they pick a mix of private an non-private and only see confirmation for some channels.
Also, what if there are 30 private channels selected ? This modal would not really work right ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, I agree; technically, may not be only channels.
Will do from private source(s): ...
and limit to 3 elements with ellipsis
@gabhubert PMRR, happy to change if need be
06b8b12
to
ba61ddf
Compare
Description
Context threads here and here
Private channels in which the Dust bot has been invited are now visible to sync by the admin, with warning.
Looks like this:
and this
Risk
The PR in itself is low risk (small code change + UX). The product risk is higher but has been discussed, see threads
Deploy Plan