Merge pull request Hacker0x01#433 from Hacker0x01/slack-connect

martijnrusschen · web-flow · commit 26f17b394d25 · 2021-07-23T08:47:49.000+02:00
diff --git a/docs/programs/slack-shared-channels.md b/docs/programs/slack-shared-channels.md
@@ -35,10 +35,8 @@ To join HackerOne’s Slack workspace as a guest:
 4.[Set up two-factor authentication](https://slack.com/intl/en-gb/help/articles/204509068-Set-up-two-factor-authentication) (2FA). (*Note: Be sure not to authenticate using SMS. Always use an authentication app to enable 2FA.*)
 
 ### About HackerOne's Slack
-HackerOne uses Slack’s [Enterprise Grid](https://slack.com/help/articles/360004150931-What-is-Slack-Enterprise-Grid) with [Encryption Key Management](https://slack.com/enterprise-key-management?cvosrc=helpcenter.helpcenter.helpcenter_ekm_help_center&cvo_creative=&utm_medium=helpcenter&utm_source=helpcenter&utm_campaign=_helpcenter_helpcenter____ob-_cr-_ym-) (EKM) enabled. When inviting customers to HackerOne’s Slack, HackerOne uses a workspace in our grid, hackerone-customer.slack.com. By default, HackerOne doesn’t make these channels private as the workspace is already restricted to a subset of HackerOne employees. In order to provide the best level of service, HackerOne avoids making these channels private so no one is prevented from supporting a customer when another employee is on vacation or leaves the organization. Customers who share channels with HackerOne won’t have access to this workspace at all, and customers who have access as guests will have access only to the channels that are relevant to their organization(s). 
+HackerOne uses Slack’s [Enterprise Grid](https://slack.com/help/articles/360004150931-What-is-Slack-Enterprise-Grid) with [Enterprise Key Management](https://slack.com/enterprise-key-management?cvosrc=helpcenter.helpcenter.helpcenter_ekm_help_center&cvo_creative=&utm_medium=helpcenter&utm_source=helpcenter&utm_campaign=_helpcenter_helpcenter____ob-_cr-_ym-) (EKM) enabled. When inviting customers to HackerOne’s Slack, HackerOne uses workspaces in our grid, including but not limited to hackerone-customer.slack.com, h1-pentest.slack.com, and h1-campaigns.slack.com. HackerOne makes these channels private or public at its discretion based on a number of factors. These workspaces are already restricted to a subset of HackerOne employees. In order to provide the best level of service, HackerOne avoids making some of these channels private so no one is prevented from supporting a customer when another employee is on vacation, the needs of the customer or project changes, or when employee leaves the organization. Customers who share channels via [Slack Connect](https://slack.com/help/articles/115004151203-A-guide-to-Slack-Connect) with HackerOne won’t have access to this workspace at all, and customers who have access as guests will have access only to the channels that are relevant to their organization(s). 
 
-The use of Slack’s EKM enables HackerOne to own the encryption keys for all of HackerOne’s Slack workspaces including `hackerone-customer.slack.com`. (*Note: Slack does not yet support EKM on shared channels.*)
+The use of Slack’s EKM enables HackerOne to own the encryption keys for all of HackerOne’s Slack workspaces, including `hackerone-customer.slack.com`. With regards to Slack Connect channels, Slack respects the individual workspaces and organizations settings for each message sent. Messages posted by HackerOne respect our settings, and messages sent from other organizations respect their settings and encryption.
 
-All employees of HackerOne access Slack using Single Sign-On provided by our identity provider, Okta, along with Multi-Factor Authentication backed by Duo. Access to the Hackerone-customer workspace is limited to customer success team members, limited amounts of sales and product members, and administrators of the HackerOne Enterprise Grid organization (IT staff).
-
-Note: HackerOne is migrating customer workspaces and there may be some users on our legacy workspace `hackerone-managed.slack.com` until this migration is complete ideally by end of Q2 2020
+All employees of HackerOne access Slack using Single Sign-On provided by our identity provider, Okta, along with Multi-Factor Authentication backed by Duo. Access to the external-facing Slack workspaces is limited to Customer Success team members, and a subset of employees, such as Product Managers, to enable their core job functions. In addition, administrators of the HackerOne Enterprise Grid organization (IT staff) have access to all of HackerOne's workspaces.
