Skip to content
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.

Feature request: Channel whitelist #91

Open
otterley opened this issue May 22, 2016 · 3 comments
Open

Feature request: Channel whitelist #91

otterley opened this issue May 22, 2016 · 3 comments

Comments

@otterley
Copy link

By default, anyone can invite Lita into any Slack channel. In certain environments this may be undesirable. For example, one might want to extend Lita to perform dangerous operations and the people who can tell her to do those things should be restricted. While one can use Lita's authorization groups feature to implement this, it is sometimes easier to keep her open but only accessible via a restricted channel.

Make it possible to specify a Slack channel whitelist for Lita. If specified, and Lita is invited to a channel in which she doesn't belong, optionally say something, and leave immediately.

@otterley
Copy link
Author

This is not possible at this time because channels.leave isn't available to bots per the API. I've filed a support request with Slack to find out why.

@otterley
Copy link
Author

A related way to control Lita may be to have her ignore public (non-DM) messages sent to her via non-whitelisted channels. I'll file a separate issue for that.

@mfischer-zd
Copy link

mfischer-zd commented May 23, 2016

Here's what Slack support said:

... opening up the *.leave methods for bots is something that is under consideration at the moment. Currently the only alternative is to /kick the bot from the channel after they are added. This could also be done via the API using the channels.kick method (which requires the channels:write permission scope). Doing it this way would potentially allow your bot to check it's 'channel whitelist' then trigger a call to the channels.kick method if the check fails.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants