# HackerOne Code

## HackerOne Code

- [Introduction to HackerOne Code for On-Premise Integrations](https://docs.pullrequest.com/on-premise-server/master.md): For integrating HackerOne Code with self-hosted (on-premise) source code provider instances.
- [Create User Account & Organization](https://docs.pullrequest.com/on-premise-server/create-pullrequest-account-and-organization.md): Creating an organization is the first step for the PullRequest Proxy integration. In order to create the organization, we'll need to be able to associate it with at least 1 active user account.
- [Installing the PullRequest Proxy](https://docs.pullrequest.com/on-premise-server/installing-the-pullrequest-proxy.md): When your organization has been created, you should receive a link via email (or other specified delivery) containing the HackerOne's PullRequest Proxy as a compressed package tarball.
- [Configuring your Proxy to Connect to the PullRequest Server](https://docs.pullrequest.com/on-premise-server/connecting-your-proxy-with-pullrequest.md): The following are steps outlining the process for configuring your PullRequest Proxy so that it can communicate with the PullRequest server.
- [Configure Posting User](https://docs.pullrequest.com/on-premise-server/configure-posting-user.md): The proxy interacts with your on premise Bitbucket or GitLab instance through a "PullRequest" member of your group.
- [Configure GitHub Posting User](https://docs.pullrequest.com/on-premise-server/configure-posting-user/configure-github-posting-user.md): The service interfaces with users in GitHub projects through a "HackerOne" member of your GitHub team. So a GitHub user must be created and configured as a Posting or Service user.
- [Configure Bitbucket Posting User](https://docs.pullrequest.com/on-premise-server/configure-posting-user/configure-bitbucket-posting-user.md): The service interfaces with users in Bitbucket projects through a "HackerOne" member of your Bitbucket team. So a Bitbucket user must be created and configured as a Posting or Service user.
- [Configure GitLab Posting User](https://docs.pullrequest.com/on-premise-server/configure-posting-user/configure-gitlab-posting-user.md): The service interfaces with users in GitLab projects through a "HackerOne" member of your GitLab team. So a GitLab user must be created and configured as a Posting or Service user.
- [Configure Azure DevOps Posting User](https://docs.pullrequest.com/on-premise-server/configure-posting-user/configure-azure-devops-posting-user.md): The service interfaces with users in Azure DevOps projects through a "HackerOne" member of your Azure DevOp team. So a Azure DevOp user must be created and configured as a Posting or Service user.
- [Configuring SSL](https://docs.pullrequest.com/on-premise-server/configuring-ssl.md): This page outlines how to configure the HackerOne's PullRequest Proxy to use SSL.
- [Start the PullRequest Proxy](https://docs.pullrequest.com/on-premise-server/start-the-pullrequest-proxy.md): Configure the PullRequest Proxy service to run.
- [Verify Data on HackerOne Code](https://docs.pullrequest.com/on-premise-server/verify-data-on-pullrequest.md)
- [Configure Webhooks](https://docs.pullrequest.com/on-premise-server/configure-webhooks.md): Webhooks allow the PullRequest application to be more responsive.
- [Configure GitHub Webhooks](https://docs.pullrequest.com/on-premise-server/configure-webhooks/configure-github-webhooks.md): After the GitHub posting user has been created and the repositories are populating in the HackerOne Code dashboard successfully, the GitHub webhooks can be configured.
- [Configure Bitbucket Webhooks](https://docs.pullrequest.com/on-premise-server/configure-webhooks/configure-bitbucket-webhooks.md): After the Bitbucket posting user has been created and the repositories are populating in the HackerOne Code dashboard successfully, the Bitbucket webhooks can be configured.
- [Configure GitLab Webhooks](https://docs.pullrequest.com/on-premise-server/configure-webhooks/configure-gitlab-webhooks.md): After the GitLab posting user has been created and the repositories are populating in the HackerOne Code dashboard successfully, the GitLab webhooks can be configured.
- [Configure Azure DevOps Webhooks](https://docs.pullrequest.com/on-premise-server/configure-webhooks/configure-azure-devops.md): After the Azure DevOps posting user has been created and the repositories are populating in the HackerOne Code dashboard successfully, the Azure DevOps webhooks can be configured.
- [Next Steps](https://docs.pullrequest.com/on-premise-server/next-steps.md)
- [Project Visibility in the HackerOne Code Dashboard](https://docs.pullrequest.com/on-premise-server/next-steps/project-visibility-in-the-pullrequest-dashboard.md)
- [Manually Requesting Validation With Posting User](https://docs.pullrequest.com/on-premise-server/assigning-code-reviews-with-posting-user.md)
- [Advanced Proxy Configuration](https://docs.pullrequest.com/on-premise-server/advanced-proxy-configuration.md): This page covers optional tuning settings not included in the setup walkthrough.
- [Upgrading PullRequest Proxy](https://docs.pullrequest.com/on-premise-server/upgrading-the-pullrequest-proxy.md)
- [PullRequest Proxy Dataflow Diagram](https://docs.pullrequest.com/on-premise-server/pullrequest-proxy-dataflow-diagram.md)