But it figured out it's impossible, you have to make answer from your own bot. And I was curios - is it possible to make similar answer from When you use github or asana slash command in slack private channel - you will receive response from But when some action happened on our side, it was impossible to send message with When user types slash command in private channel, it's actually possible to answer him with ephemeral (visible only for him) messages, so there wasn't any problem with subscription procedure.
So, the issue was - I built a bot that subscribes slack channel for some notifications (some actions in our project). It also does not work for direct messaging channel or existing private channel. However, an obvious disadvantage is that it creates more work for the admin team (which could partly be compensated by automating with scripts).
With this approach and all apps installed by this user can have full access to all private channel (with the correct scopes). Restrict removal of users from private channels to adminsĪll new private channels are create by the admin team, needs to be a member creation of new private channels to admins Its not pretty, but its works:Ĭreate a generic admin user, e.g. If you want to have more control over your private channels you can address this with a process based workaround. I agree that this may seam a bit unusual, since on many platforms a admin or superuser has access to everything. Its part of Slack's security architecture, that one can only ever see channels that he (or the user that the access token is created from) is a member of (except for public channels of course).
0 kommentar(er)
