Skip to main content

Bitbucket proof types and permissions

Hyperproof supports collecting information directly from Bitbucket.

When you create a Bitbucket Hypersync on controls or labels you can automatically collect the following proof:

  • List of Commits

  • List of Pull Requests

  • List of Users

Requirements

To connect to Bitbucket and collect proof your Bitbucket configuration must meet the following requirements.

  • An administrator on Bitbucket must create Workspace Access Tokens for use by Hyperproof. In Bitbucket: select a workspace; click Settings > Workspace settings > Access tokens > Create Workspace Access Token. Select all the scopes and click Create.

  • Repeat for each workspace from which you need to gather proof

Note

Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance meeting the requirements to integrate with Hyperproof and collect the proof you need.

Connection configuration

When you create a Bitbucket Hypersync for the first time you must provide the following information:

  • Workspace name - the workspace from which to gather proof

  • Access token - enter the Access token that Hyperproof should use to access the Bitbucket workspace.

Note

You only need to connect Hyperproof to the app once, and then you can create as many Hypersyncs as you need. Additionally, you can create multiple Hypersyncs for a single control or label.

Additional documentation