Skip to content
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

[BUG]: Slack permission #913

Closed
raghav39 opened this issue Mar 28, 2023 · 3 comments
Closed

[BUG]: Slack permission #913

raghav39 opened this issue Mar 28, 2023 · 3 comments
Labels
🤷‍♂️ action required Further action or information required ⭐ enhancement New feature or request

Comments

@raghav39
Copy link

Describe the bug
Is it possible to avoid the slack bot permission to read the messages from all public channels even if the bot is not part of?

Screenshots
Screenshot 2023-03-28 at 7 59 42 PM

@abuaboud abuaboud added the 🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces label Mar 28, 2023
@abuaboud
Copy link
Contributor

abuaboud commented Mar 29, 2023

Currently, both the frontend request all app permissions might be required.

Even though channels:history required for the new message trigger. Allowing the user to choose the permissions may lead to a bad user experience, as mentioned in this related issue: #803.

Instead, for this use case, I suggest creating your own OAuth2 application on Slack, luckily which is a easy process for slack. and use your own app credentials instead of activepieces.

Does this works? Let me know what do you think?

@abuaboud abuaboud added ⭐ enhancement New feature or request 🤷‍♂️ action required Further action or information required and removed 🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces labels Mar 29, 2023
@raghav39
Copy link
Author

Yep, that would work. Thanks :)

@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If this issue is continuing with the lastest stable version of Activepieces, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤷‍♂️ action required Further action or information required ⭐ enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants