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

Skip to content

Commit 6ba62a4

Browse files
authored
Merge pull request Hacker0x01#631 from Hacker0x01/child-projects
Update - Remove info
2 parents c2a57f3 + 8742f3f commit 6ba62a4

File tree

1 file changed

+3
-8
lines changed

1 file changed

+3
-8
lines changed

docs/programs/parent-child-programs.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,22 +4,17 @@ path: "/programs/parent-child-programs.html"
44
id: "programs/parent-child-programs"
55
---
66

7-
There are various programs on HackerOne that are associated with a larger organization. Such programs are referred to as parent/child programs, where the parent program is the primary account, and any subsequent child is a subordinate program that is linked to the parent. For instance, an organization (the parent) could be comprised of multiple different companies (the children), each with their own HackerOne program that has their own budget and management. Or, they can also be organizations that have set up multiple programs for each of their products.
7+
There are various programs on HackerOne that are associated with a larger organization. Such programs are referred to as parent/child programs, where the parent program is the primary account, and any subsequent child is a subordinate program that is linked to the parent.
88

9-
Child programs still function as their own program in which they still need to:
10-
* Set their own program settings
11-
* Invite their own hackers
12-
* Manage their own reports
13-
14-
However, parent/child programs are still able to function and work together by:
9+
Child programs are subsidiaries of their parent programs. They are able to function together by:
1510
* Sharing a bounty pool
1611
* Transferring reports between programs
12+
* Reporting to the same cyber security team
1713

1814
### Sharing a Bounty Pool
1915
Parent/child programs have the option to share a bounty pool so that the main organization doesn’t need to allocate specific dollar amounts for each program, but rather, they can pull their funds from a master pool. This will prevent programs from being blocked in having to contact HackerOne to manually transfer funds between programs. Programs can opt-in to this feature if they’re using the prepayment method to pay bounties.
2016

2117
When you opt-in to this feature, the parent program is able to keep track of the total amount of funds used from each child program so that they don’t need to access each account separately.
22-
![parent-child-programs-1](./images/parent-child-programs-1.png)
2318

2419
### Transferring Reports between Parent/Child Programs
2520
Parent programs can transfer reports to child programs and vice versa. As the report is transferred from one program to another, it appears in the transferred program’s inbox with an activity log about the transfer.

0 commit comments

Comments
 (0)