> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/git-and-version-control/git/bitbucket-cloud-connect-app.md).

# Bitbucket Cloud Connect app

Connect Zerve to all the repositories in a Bitbucket workspace.

Use the **Cloud Connect app** to give Zerve access to every repository in a Bitbucket workspace. For access tied to one user instead, use the [Bitbucket OAuth consumer](/zerve-docs/git-and-version-control/git/bitbucket-oauth-consumer.md).

{% stepper %}
{% step %}

### Open Git Integration

Go to **Git Integration** in your individual or organization settings. See [Individual or organization?](/zerve-docs/git-and-version-control/git.md#individual-or-organization)
{% endstep %}

{% step %}

### Choose the Cloud Connect app

In **Git Management Service**, choose **Bitbucket**. Under **Bitbucket Installation Type**, choose **Cloud Connect App**, then select **Install**.
{% endstep %}

{% step %}

### Choose the workspace

Bitbucket lists your workspaces. Choose the one to connect, and select **Grant Access**. You're returned to Zerve.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/git-and-version-control/git/bitbucket-cloud-connect-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.