Required Permissions
PlayerZero connects to Bitbucket using OAuth and inherits permissions from the authenticated user. Admin access is not required unless restricted repositories need to be accessed.
- Read repository files and structure
- Analyze pull requests and post automated comments
- Access basic account metadata (e.g., username, email)
Access is limited to only the repositories you explicitly select during the OAuth authorization process. PlayerZero does not request or retain broader access than what your Bitbucket user account already has permission to see.
Basic Setup Guide
Prerequisites
- A PlayerZero account. You can get started by creating an account.
- Admin access to your Bitbucket workspace to:
- Authorize OAuth applications
- Grant repository access permissions
- Configure integration settings
1. Authorize PlayerZero OAuth Application
Connect your Bitbucket workspace to PlayerZero through OAuth:- Navigate to Settings → Code in your PlayerZero dashboard
- Select Bitbucket from the available SCM providers
- Click “Connect to Bitbucket” - this will redirect you to Bitbucket’s OAuth authorization page
- Select your Bitbucket workspace
- Review the requested permissions and click “Grant access”
- You’ll be redirected back to PlayerZero with authorization complete
2. Configure Repository Access
After OAuth authorization, configure which repositories PlayerZero should monitor:About Projects: A project in PlayerZero is a workspace that combines your application’s repositories with telemetry data, user sessions, and ticketing systems. Connect repositories and tickets that are relevant to your project’s monitoring goals to correlate code changes, user behavior, and reported issues.
-
Navigate to Repository Settings
- Go to your project Settings → Repositories
-
Import Repositories
- In the “Import Repository” section, click the “Select a Provider” dropdown
- Choose your Azure DevOps organization from the list
- PlayerZero will display all available repositories from your organization
-
Add and Configure Repositories
- Click “Import” next to each repository you want to monitor
- Select repositories containing code relevant to your project (frontend, backend, or full-stack repos)
- For each connected repository in the “Connected Repositories” section:
- Set Primary Branch: Click the branch button (e.g., “main”) to select which branch to monitor
- Toggle Active Status: Use the toggle switch to enable/disable monitoring
PlayerZero only accesses repositories you explicitly grant permission to. Repository data is not imported until you enable specific repositories in your PlayerZero settings.
3. Repository Synchronization
Once enabled, PlayerZero will begin importing and analyzing your repository data:- Initial sync may take several minutes to hours depending on repository size
- PlayerZero will sync new commits and pull requests automatically
- Monitor progress in the Settings → Code section
Token Management - OAuth Token Refresh
PlayerZero automatically manages OAuth token refresh:
- OAuth tokens are refreshed automatically when they expire
- No manual intervention required for token management
- If authorization fails, you’ll receive a notification to re-authorize
Re-authorization
If you need to re-authorize the connection:- Navigate to Settings → Code in your PlayerZero dashboard
- Find your Bitbucket connection and click “Reconnect”
- Follow the OAuth flow again to re-establish the connection
Bitbucket Server Setup
For Bitbucket Server installations, additional configuration may be required:Prerequisites:
- Bitbucket Server with API access enabled
- Network connectivity between PlayerZero and your Bitbucket Server instance
- Admin access to configure OAuth applications