With Slack’s updated UI, more of our users are requesting shared channels. What’s your approach...

  • 3 September 2020
  • 4 replies


With Slack’s updated UI, more of our users are requesting shared channels. What’s your approach to approving or denying shared channel requests (e.g., what guidelines have you set up and communicated to your users about when you will or won’t approve these requests)?

🗨 Link to Slack thread

4 replies

Following, as it’s something I’m considering to add more rigour too when time permits.
ATM, we do something like this :
• All requests pipe into a slack-admin channel, where all slack admins are members. This is done to centralise the request, and to provide transparency re discussions and/or approval.
• Naming conventions - currently a soft enforcement, but I require both company names to be included in the channel name.
• Noted owner - we try to have an appointed owner that is responsible for the shared channel and comms therein. This is currently fuzzy, and tricky to enforce/maintain.
Ideally, I’d like to see some form a review of shared channels and usage thereof, and cleanup stale channels, etc.

This works for us as a soft guideline today, but there is a need to tighten up a bit while still allowing agility.

Would be great to hear other approaches.

Userlevel 1

I manually collect all the requests from the Admin Console (not ideal) then group DM 8 people at time asking them to complete a `Slack Connect Request` form which collects the request data in case anyone wants to audit later.

I also created a workflow in our Slack support channel called `Share Channel Externally` which explains the Slack Connect/Shared Channel process and also supplies the link to the request form.

Open Thread in Slack

Everything is funneled through our ticketing system. We have documentation explaining everything needed on their end to make it happen. We also require NDA’s to be signed off before any work is done.