-
Notifications
You must be signed in to change notification settings - Fork 23
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
[Proposal] Access control for Summaries based on Slack account #7
Comments
Hi! That sounds nice. but... My team member have mixed public channel and private group(or his one) messages. So, I'm wondering... |
You mean that your team sometime uses message from Private Group to add "supplementary explanations", right? If my understanding is right, there might be few choices:
I know (2) is a stupid workaround and little bit "Not user friendly" spec but might be easy to realize. Of course, other ideas are welcomed. |
Oh, I had an another one. "3. Make a new option But I don't think this is a good one. I hate too many options 😞 |
Yes 😄 I also think (1) is good. |
Thank you for your comments! I will first implement access control feature (without 1,2,3) for my team. |
I have implemented access control based on Slack channels/groups. If a summary contains a message in a private channel, the summary can be viewed by the users which belong to the channel. However this implementation doesn't contain the "Comment function". |
Thank you for this nice product.
My team is using Togelack to keep important conversations for later reference.
It improved our communication greatly!
While using, we have noticed that summarizing messages in Private Channel is danger because everyone can read every Summary.
So my proposal is to add access control to each Summaries.
My idea is simple: In Private Mode, When user opening (or listing) a Summary, check all messages in that for their channel and allow him to do it only when he can access to all of them.
How do you think about this idea?
If this sounds nice, I will try to implement this feature.
The text was updated successfully, but these errors were encountered: