Table of contents
Bitbucket Setup
WorkSights connects to Bitbucket using OAuth 2.0. Setup takes a few minutes.
For an overview of how Bitbucket activity appears in WorkSights, see Bitbucket Integration Overview.
Connecting Bitbucket
Step 1: Start the Connection
- Go to Services in the top navigation
- Find Bitbucket in the list
- Click Connect Bitbucket
Only Admins, Executives, and Owners in WorkSights can initiate this connection.
Step 2: Authorize WorkSights in Bitbucket
You'll be redirected to Bitbucket to authorize the connection. You must be an owner of the Bitbucket workspace you're connecting — not just a workspace or repository admin. This is a Bitbucket requirement, not a WorkSights choice: only a workspace owner can install the workspace-wide webhook the connection depends on. If you connect as a member who isn't an owner, the connection will be rejected with a message telling you so — reconnect with an account that owns the workspace instead.
WorkSights requests read-only access to your account identity, repositories, pull requests, issues, and projects, plus the ability to register a webhook. WorkSights never requests write, delete, or admin access to your repositories.
Step 3: Review Workspace Coverage
One connection covers every repository in your Bitbucket workspace, including repositories created after you connect — there's nothing further to configure per repository.
What Happens Next
Once connected, WorkSights begins setting up your Bitbucket workspace to bring commit, pull request, and code review activity onto the timeline. Activity capture for Bitbucket is rolling out, so there may be a delay before the first activity appears — this is expected.
Connection settings can be reviewed and updated at any time from the integration page.