> ## Documentation Index
> Fetch the complete documentation index at: https://docs.endorlabs.com/llms.txt
> Use this file to discover all available pages before exploring further.
## Submitting Feedback
If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:
POST https://docs.endorlabs.com/feedback
```json
{
"path": "/setup-deployment/scm-integrations/bitbucket-datacenter-app/manage-bitbucket-datacenter-app/index",
"feedback": "Description of the issue"
}
```
Only submit feedback when you have something specific and actionable to report.
# Manage Bitbucket Data Center App on Endor Labs
> Learn how to manage your Bitbucket App integration in Endor Labs.
You can make changes to the Bitbucket Data Center App integrations or delete them. You can view the activity logs for the Bitbucket Data Center App and rescan your Bitbucket projects on demand.
1. Sign in to Endor Labs and select **Integrations** from the left sidebar.
2. Click **Manage** next to **Bitbucket Data Center** under **Source Control Managers**.
3. Click the three vertical dots next to the integration.
You can choose from the following options:
* [**Update Credentials**](#update-credentials)
* [**Edit Integration**](#edit-bitbucket-data-center-app-integration)
* [**View Sync Log**](#view-sync-logs)
* [**Delete Integration**](#delete-endor-labs-bitbucket-data-center-app)
### Update Credentials
To update the Bitbucket Data Center App credentials:
1. Click the vertical three dots next to the integration, and select **Update Credentials**.
2. You can update your **HTTP Access Token**.
3. Select **Save**.
You cannot update the Bitbucket organization URL. To monitor a different path, create a new installation.
### Edit Bitbucket Data Center App integration
To edit the Bitbucket Data Center App integration:
1. Click the three vertical dots next to the integration, and select **Edit Integration**.
2. Select the scan types to enable in **Scanners**.
3. Select **Pull Request Settings** to edit the PR scans configuration.
See [Bitbucket Data Center App PR scans](/setup-deployment/scm-integrations/bitbucket-datacenter-app/bitbucket-datacenter-pr-scans) for more information.
**Permissions for the HTTP access token**
The HTTP access token must have at least write access for Repositories and read access for Projects. See [Create an access token](/setup-deployment/scm-integrations/bitbucket-datacenter-app/bitbucket-datacenter-pr-scans#create-an-http-access-token) for more information.
4. Click **Start Scannning Repositories**.
The changes are applied from the next scanning cycle.
### Delete Endor Labs Bitbucket Data Center App
To delete a Bitbucket Data Center App integration, click the three vertical dots next to the integration, and select **Delete Integration**.
You must also delete the webhook in Bitbucket Data Center after deleting the integration in Endor Labs. See [delete webhooks in Bitbucket Data Center](#delete-configured-webhooks-in-bitbucket-data-center)
When you delete the integration, it also deletes all child namespaces, projects, and references associated with the auto-generated root group namespace. It also deletes any manually created namespaces and projects under auto-generated namespace.
Delete the existing integration and create a new one in Endor Labs if you modify the Bitbucket Data Center project host URL.
#### Delete configured webhooks in Bitbucket Data Center
After deleting the Bitbucket Data Center app in Endor Labs, ensure that all project-level webhooks created for Endor Labs are also removed in your Bitbucket Data Center instance.
To delete a project-level webhook in Bitbucket Data Center:
1. Log in to your Bitbucket Data Center instance and navigate to your project.
2. Select **Project Settings** from the left sidebar.
3. Select **Webhooks** from the left sidebar.
4. Locate the webhook created for Endor Labs.
5. Click three dots under **Actions** and select **Delete**.
Repeat these steps for each project that has an Endor Labs webhook.
### View sync logs
Endor Labs detects and reports installation and synchronization errors during organization sync. These include expired tokens, insufficient permissions, invalid host configurations, and certificate issues. Sync logs report those errors that you can resolve.
To view sync logs, click the three vertical dots next to the integration, and select **View Sync Logs**.
The sync logs display details of synchronization attempts, including timestamps, error types, and diagnostic messages. These logs help identify issues such as authentication failures or configuration problems.
#### Types of errors
The sync logs detect and display the following categories of sync failures:
* **Expired or invalid Personal Access Tokens (PATs)**: The PAT used for authentication has expired or is no longer valid. Edit the integration and provide a valid token.
* **Insufficient PAT permissions**: The PAT does not have the required scopes, such as repository read access. You must generate and provide a PAT with the correct access.
* **Certificate related access issues**: The certificates required to connect to the SCM are invalid, outdated, or untrusted. This error occurs in self-hosted GitLab instances that use custom SSL certificates. Update the certificate configuration or ensure the certificate chain is properly trusted to resolve the issue.
* **Incorrect or invalid host URLs**: The configured URL is incorrect or unreachable. Since you cannot edit the host URL, you need to delete and reinstall the integration using the correct URL.
After you resolve the issue, the error is automatically cleared during the next successful scan. You can manually re-trigger the scan using **Rescan Org** to verify the resolution immediately.
### Manually rescan Bitbucket Data Center projects
Bitbucket Data Center App scans your repositories every 24 hours. Click **Rescan Org** to manually trigger a scan outside the 24-hour period.
### Add more Bitbucket projects to scan
Click **Scan More Repositories** to go to **Projects**, where you can add more projects to scan through the Bitbucket Data Center App.