diff --git a/docs/programs/images/multi-party-coordination-1.png b/docs/programs/images/multi-party-coordination-1.png new file mode 100644 index 00000000000..3872118d686 Binary files /dev/null and b/docs/programs/images/multi-party-coordination-1.png differ diff --git a/docs/programs/multi-party-coordination.md b/docs/programs/multi-party-coordination.md new file mode 100644 index 00000000000..25ba229fb6b --- /dev/null +++ b/docs/programs/multi-party-coordination.md @@ -0,0 +1,13 @@ +--- +title: "Multi-Party Coordination" +path: "/programs/multi-party-coordination.html" +id: "programs/multi-party-coordination" +--- + +Sometimes individual reports, disclosed or undisclosed, must be shared with 3rd parties that are not your program team members or a hacker participating in your program. This could be for many purposes such as patch development, information sharing, etc. + +The only requirement to use this feature is for the report participant being added to have an email address. If your intended report participant already has a HackerOne account they will be notified of their addition to the report. If not, they will be prompted to sign up for a HackerOne account to view the report. Current HackerOne users may also be added via username instead of email address. + +Report participants have read access only to the report(s) they are added to and may write comments visible to all parties on the report. + +![multi-party-coordination-1](./images/multi-party-coordination-1.png) \ No newline at end of file diff --git a/src/pages/programs/programs-nav.yaml b/src/pages/programs/programs-nav.yaml index e2cb6435272..50c77546d1e 100644 --- a/src/pages/programs/programs-nav.yaml +++ b/src/pages/programs/programs-nav.yaml @@ -288,6 +288,8 @@ path: /programs/import-vulnerabilities.html - title: IP Allowlists path: /programs/ip-allowlists.html + - title: Multi-Party Coordination + path: /programs/multi-party-coordination.html - title: Password Best Practices path: /programs/passwords.html - title: Proof of Compliance