> ## 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-cloud/manage-bitbucket-cloud/index",
"feedback": "Description of the issue"
}
```
Only submit feedback when you have something specific and actionable to report.
# Manage Bitbucket Cloud App on Endor Labs
> Learn how to manage your Bitbucket App integration in Endor Labs.
You can make changes to the Bitbucket Cloud App integrations or delete them. You can view the activity logs for the Bitbucket Cloud 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 Cloud** 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-cloud-app-integration)
* [**View Sync Log**](#view-sync-logs)
* [**Delete Integration**](#delete-endor-labs-bitbucket-cloud-app)
### Update Credentials
To update the Bitbucket Cloud App credentials:
1. Click the three vertical dots next to the integration, and select **Update Credentials**.
2. You can update the credentials used when you [installed the Bitbucket Cloud App](/setup-deployment/scm-integrations/bitbucket-cloud#install-the-bitbucket-cloud-app) by updating either the access token or the email and API token.
3. Click **Save**.
You cannot update the Bitbucket organization URL. To monitor a different path, create a new installation.
### Edit Bitbucket Cloud App integration
To edit the Bitbucket Cloud 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 Cloud App PR scans](/setup-deployment/scm-integrations/bitbucket-cloud/bitbucket-cloud-pr-scans) for more information.
**Permissions for your credentials**
Ensure that the credentials have the required permissions for the selected authentication method. See [Create an access token](/setup-deployment/scm-integrations/bitbucket-cloud/bitbucket-cloud-pr-scans#create-an-access-token) or [Create an API token](/setup-deployment/scm-integrations/bitbucket-cloud/bitbucket-cloud-pr-scans#create-an-api-token) for more information.
4. Click **Start Scanning Repositories**.
The changes are applied from the next scanning cycle.
Click **Rescan Org** after editing the integration to apply changes immediately instead of waiting for the next scheduled scan.
### Delete Endor Labs Bitbucket Cloud App
To delete a Bitbucket Cloud App integration, click the three vertical dots next to the integration, and select **Delete Integration**.
When you delete the integration, it will also delete 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.
The workspace or project URL cannot be edited in an integration.
Delete the existing one and create a new integration in Endor Labs in the following scenarios to prevent duplication of findings in your tenant:
* You modify the Bitbucket Cloud workspace or project host URL.
* You want to update the integration to workspace level from project level.
### 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 projects
Bitbucket Cloud 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 Cloud App.