8000 fixes · SaFiSec/docs.hackerone.com@19cb705 · GitHub
[go: up one dir, main page]

Skip to content {"props":{"docsUrl":"https://docs.github.com/get-started/accessibility/keyboard-shortcuts"}}

Commit 19cb705

Browse files
committed
fixes
1 parent 144a6e7 commit 19cb705

File tree

5 files changed

+24
-24
lines changed

5 files changed

+24
-24
lines changed

docs/programs/program-start-up-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,5 +21,5 @@ HackerOne Bounty | A continuous security program in which trusted hackers are in
2121
![getting-started-1](./images/getting-started-1.png)
2222

2323
### Next Steps
24-
* [Start H1 Response](start-h1-response.html) or [Start H1 Bounty](start-h1-bounty.html).
24+
* [Start HackerOne Response](start-h1-response.html) or [Start HackerOne Bounty](start-h1-bounty.html).
2525
* [Contact HackerOne](https://support.hackerone.com/hc/en-us/requests/new) to work with one of our program managers to get guidance on setting up your program.

docs/programs/slack-integration.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,29 +6,29 @@ id: "programs/slack-integration"
66

77
With Slack integration, your team can stay up to date on HackerOne report activities without needing to leave Slack. Activities such as report triaged, bounty paid, and new comments added will trigger notifications in your selected channel. You can customize which activities you want to be notified about in which channels so that teams can only see what’s relevant to them.
88

9-
<i>Note: Slack integration is only available to H1 Response and H1 Bounty Pro (and above) customers. For more details, see product editions. Existing users of the Slack integration will also need to navigate to **Settings > Program > Integrations > Slack** to enable the new settings.</i>
9+
<i>Note: Slack integration is only available to HackerOne Response and HackerOne Bounty Pro (and above) customers. For more details, see product editions. Existing users of the Slack integration will also need to navigate to **Settings > Program > Integrations > Slack** to enable the new settings.</i>
1010

1111
### Set Up Slack Integration
1212
To set up slack integration:
1313
1. Go to **Settings > Program > Integrations**.
14-
2. Click the **Connect with Slack** link.
14+
2. Click the **Connect with Slack** link.
1515
![slack-integration-2](./images/slack-integration-2.png)
16-
3. Click **Authenticate with Slack**.
16+
3. Click **Authenticate with Slack**.
1717
4. You'll be redirected to a Slack authorization screen where you'll be asked to grant HackerOne permissions to access your team. *Note: If you have multiple Slack teams, select the one you want HackerOne to post to.*
1818
5. Click **Authorize** and you'll be redirected back to HackerOne to continue the setup of your Slack notifications. <br> *Note: the following privileges are necessary for HackerOne to successfully set up Slack Integration:*
1919
* **Access information about your public channels** is needed to allow the admin configuring the integration to see all your current Slack channels which they can assign notifications towards.
2020
* **View email addresses of people on your team** is needed in order to set up username mapping between H1 and Slack for proper mentions.
2121
* **Access your team's profile information** is a standard permission for all Slack integrations. At this time, we don't have a way to reduce permissions if customers don't want to use all of these features.
22-
23-
Check out the FAQ section at the bottom of this page to understand why HackerOne needs access to so many permissions.
22+
23+
Check out the FAQ section at the bottom of this page to understand why HackerOne needs access to so many permissions.
2424

2525
### Add Notification Configuration for Slack
2626
You can configure specific HackerOne activities you'd like to receive Slack notifications for.
2727

2828
To set up your notification configuration:
2929
1. Go to your Slack integration settings in **Settings > Program > Integrations**.
3030
2. Click **Create your first Notification Configuration**.
31-
3. Select the public channel to post to in the **Post to Channel** field.
31+
3. Select the public channel to post to in the **Post to Channel** field.
3232
4. <i>(Optional)</i> Select **I want to use a private channel** to post your notification to a private channel, and manually type in the name of the private channel.
3333
![slack-integration-3](./images/slack-integration-3.png)
3434

@@ -41,30 +41,30 @@ Awards | <ul><li>Bounty suggested</li><li>A bounty has been paid</li><li>Not eli
4141
Disclosure | <ul><li>Agreed on going public</li><li>Report became public</li><li>Manually disclosed</li>
4242
Misc | <ul><li>The assignee of the report has been changed</li><li>An internal comment was added to the report</li><li>A public comment was added to the report</li><li>Report locked, hackers can't reply on the report anymore
4343

44-
5. Click **Save**.
44+
5. Click **Save**.
4545

46-
All of your selected notifications now be posted to your selected channel on Slack. To configure posting notifications to other channels, click **Add Notification Configuration** and follow steps 3-5 again.
46+
All of your selected notifications now be posted to your selected channel on Slack. To configure posting notifications to other channels, click **Add Notification Configuration** and follow steps 3-5 again.
4747

4848
### Mapping Usernames
4949
After configuring channel notifications, you have the option to map HackerOne usernames to Slack usernames. It's important to establish a link between these two usernames because when someone mentions your username in HackerOne, you’ll be notified just as if someone mentioned your username natively in Slack. This'll ensure that you're appropriately notified in Slack to pay attention to the most critical HackerOne notifications when your username is mentioned specifically for a follow-up comment or action.
5050

51-
To map usernames in your Slack settings:
52-
1. Go to the **Slack Usernames** section.
51+
To map usernames in your Slack settings:
52+
1. Go to the **Slack Usernames** section.
5353
2. Type the Slack username associated with the corresponding HackerOne user in the Slack Username field.
5454
3. Select the user from the dropdown.
55-
4. Click **Save**.
55+
4. Click **Save**.
5656

5757
![slack-integration-1](./images/slack-integration-1.png)
5858

5959
### Disconnecting Slack Integration
60-
To disconnect your slack integration, go to **Settings > Program > Integrations > Slack** and click **Disconnect** in your Slack settings.
60+
To disconnect your slack integration, go to **Settings > Program > Integrations > Slack** and click **Disconnect** in your Slack settings.
6161

6262
### FAQs
6363
#### Q: Why must I authorize HackerOne access to so many permissions for my Slack integration?
6464

6565
A: We know it’s concerning that you have to give HackerOne access to information about your public channels, the email addresses of people on your team, and access to your team’s profile information. Keep in mind that we require these permissions because we’re using the following Slack methods for integration:
6666

67-
Method | Description
67+
Method | Description
6868
------ | ------------
6969
https://api.slack.com/methods/users.list | mapping Slack users with HackerOne users
7070
https://api.slack.com/methods/channels.list | autocompleting channel chooser during setup and getting current status of the channel (if it's still valid)
@@ -78,4 +78,4 @@ https://api.slack.com/scopes/channels:read | for channels.list
7878
https://api.slack.com/scopes/chat:write:bot | for chat.postMessage
7979
https://api.slack.com/scopes/users:read | for users.list
8080

81-
Due to limitations with the API, we can’t filter information from the scopes, and so it’s necessary that access to all permissions are given in order to successfully integrate with Slack.
81+
Due to limitations with the API, we can’t filter information from the scopes, and so it’s necessary that access to all permissions are given in order to successfully integrate with Slack.

docs/programs/start-h1-bounty.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Start H1 Bounty"
2+
title: "Start HackerOne Bounty"
33
path: "/programs/start-h1-bounty.html"
44
id: "programs/start-h1-bounty"
55
---

docs/programs/start-h1-response.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Start H1 Response"
2+
title: "Start HackerOne Response"
33
path: "/programs/start-h1-response.html"
44
id: "programs/start-h1-response"
55
---
@@ -8,11 +8,11 @@ If you elect to **Start H1 Response**, you'll be taken to the Setup Guide where
88

99
![getting-started-2](./images/getting-started-2.png)
1010

11-
1. Select **Edit** to edit your policy and scope.
12-
2. Select **Edit** to edit your profile.
13-
3. *(Optional)* Click the **[Human Augmented Signal](human-augmented-signal.html)** toggle to be either on or off.
14-
4. Once you've completed all of the fields in step 1 of the Setup Guide, click **Submit for Approval** to have HackerOne review your program.
11+
1. Select **Edit** to edit your policy and scope.
12+
2. Select **Edit** to edit your profile.
13+
3. *(Optional)* Click the **[Human Augmented Signal](human-augmented-signal.html)** toggle to be either on or off.
14+
4. Once you've completed all of the fields in step 1 of the Setup Guide, click **Submit for Approval** to have HackerOne review your program.
1515
5. If your program is approved by HackerOne, your program will be placed in controlled launch where it'll remain private and visible to only a select number of hackers. To publicly launch your program, your program must:
1616
* Receive at least 10 reports and have invited 100 hackers
1717
* Meet the baseline responsiveness limits
18-
6. Once you've met the criteria, the **Public Launch** button will appear. You can publicly self-launch your program when you're ready to.
18+
6. Once you've met the criteria, the **Public Launch** button will appear. You can publicly self-launch your program when you're ready to.

src/pages/programs/programs-nav.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@
99
- title: Program Start-Up Guide
1010
path: /programs/program-start-up-guide.html
1111
items:
12-
- title: Start H1 Response
12+
- title: Start HackerOne Response
1313
path: /programs/start-h1-response.html
14-
- title: Start H1 Bounty
14+
- title: Start HackerOne Bounty
1515
path: /programs/start-h1-bounty.html
1616
- title: Private vs Public Programs
1717
path: /programs/private-vs-public-programs.html

0 commit comments

Comments
 (0)
0