Slack Shared Channels
This feature is only available to HackerOne Enterprise. For more details, please see product editions.
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.
Your workspace’s respective Slack administrator is responsible for adding members to the channel. For instance, HackerOne manages access to the channel for HackerOne members only, while your organization’s Slack admin will only grant access to members within your organization.
Either you or HackerOne can initiate the shared channel set up process. To set up a shared channel:
- Create the channel in Slack.
- Create a sharing link as per Slack’s instructions.
- Send the link for the channel to any HackerOne member.
- Wait for the HackerOne administrator to approve the channel.
- Approve the shared channel once you receive notification that the channel has been approved by HackerOne.
You can join HackerOne’s Customer Slack workspace (https://hackerone-customer.slack.com) as a guest user to have your team collaborate with HackerOne staff.
Note: It’s your responsibility to inform HackerOne in a timely manner when a member’s access is to be revoked.
To join HackerOne’s Slack workspace as a guest:
- Click the Join Now button in your Slack invitation email.
- Enter your username and create a password for your account.
- Click Create Account.
4.Set up two-factor authentication (2FA). (Note: Be sure not to authenticate using SMS. Always use an authentication app to enable 2FA.)
HackerOne uses Slack’s Enterprise Grid with Enterprise Key Management (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 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. 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 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.