Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 97d0cfc

Browse files
committed
Enterprise disclaimer
1 parent 6ba62a4 commit 97d0cfc

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/programs/slack-shared-channels.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: "Slack Shared Channels"
33
path: "/programs/slack-shared-channels.html"
44
id: "programs/slack-shared-channels"
55
---
6+
>This feature is only available to HackerOne Enterprise Advisory Plus. For more details, please see product editions.
67
78
Shared channels enable you to work with HackerOne in a single channel from your own workspace. Accessing shared channels from your own workspace enables you to adhere to the security standards of your own organization instead of having to implement the workspace login security standards of HackerOne. [Learn more about Slack’s shared channels](https://slack.com/intl/en-gb/help/articles/115004151203-A-guide-to-shared-channels).
89

@@ -35,7 +36,7 @@ To join HackerOne’s Slack workspace as a guest:
3536
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.*)
3637

3738
### About HackerOne's Slack
38-
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).
39+
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).
3940

4041
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.
4142

0 commit comments

Comments
 (0)