Skip to main content

Bitbucket proof types and permissions

Written by Hyperproof Support
Updated over 3 weeks ago

πŸ“ 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 in meeting the requirements to integrate with Hyperproof and collect the proof you need.


Hyperproof supports collecting information directly from Bitbucket.
​

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

Bitbucket proof types and fields

Proof type

Fields

Testable

List of Commits

Commit Hash, Project, Repository, Author, Description, Created On

Yes

List of Pull Requests

Pull Request Id, Project, Repository, Description, Author, Status, Created On, Updated On

Yes

List of Users

Name, User Id, Repository, Permissions, Access Type, Last Login

Yes


​

This Hypersync supports importing a user list for an access review. See Importing a list of application users with a Hypersync for more information.

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.

Connection configuration

Authentication type: Custom
​

Custom authentication parameters: Workspace Name, Access Token

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

Did this answer your question?