> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/miscellaneous-info/using-bitbucket-projects-as-workspaces.md).

# Using Bitbucket Projects as Workspaces

By default, Aikido treats your Bitbucket workspace as a single environment. Some teams, however, use Bitbucket projects to organize their repositories and want each project to appear as its own workspace in Aikido. This guide explains how to set that up.

### Prerequisites

* Currently supported only for Bitbucket.
* You need to be a Bitbucket admin

{% hint style="warning" %}
The feature must be enabled by Aikido support. Contact us via chat to activate.
{% endhint %}

### Steps

1. **Create the global Bitbucket workspace in Aikido**
   * Go through the onboarding flow
   * No need to select any repositories here; this workspace will be used to split into other projects.
2. **Access the project-based onboarding link**
   * Go to [https://app.aikido.dev/onboarding/bitbucket/connect-project-based-group](https://app.aikido.dev/onboarding/bitbucket/connect-project-based-group?utm_source=chatgpt.com)
3. **Enter your Bitbucket project key**
   * Provide the key of the project you want to create an Aikido workspace for.
4. **Select repositories**
   * Click **Next**, choose the repositories to include, and proceed.
5. **Finish setup**
   * Your project-based workspace is now created.
6. **Repeat for additional projects**
   * Switch back to your **global workspace** using the top-left dropdown.
   * Repeat from step 2 for each additional project.


---

# 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://help.aikido.dev/miscellaneous-info/using-bitbucket-projects-as-workspaces.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.