# Creating an Organization

Go to the [Org tab in Pipekit](https://pipekit.io/organization) and click on the `Create Org` button. You will be prompted to enter an organization name and a description. Once you have entered the required information, click on the `Submit` button to create your Pipekit Organization.

## Connecting your Organization to git

You will then be prompted to optionally connect your Organization to your your git provider. You can choose to connect to either GitHub or Gitlab. Connecting your Organization to git allows your users:

* to create Pipes from workflow manifests stored in your git repositories;
* to trigger pipe runs based on git events;
* to submit and manage workflowTemplates via Pipekit.

You can choose to add all your repositories or specific repositories to your Pipekit Organization.

### GitHub

1. Click the button for GitHub. It will lead you through the process to authorize Pipekit's GitHub App.
2. When prompted by GitHub, select either, "All repositories" or select the list of repositories you would like to grant Pipekit access to using the dropdown.
3. Click, "Authorize"

### Gitlab

For Gitlab, you will need to create a [Personal Access Token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html). We recommend creating a service account user in your organization on Gitlab that has access to any repositories that you want Pipekit to read from.

To connect Pipekit, click the button for Gitlab, input the Personal Access Token that you created, optionally change the Gitlab URL and click, "Submit"

### BitBucket

For BitBucket, you will need a [HTTP Access Token](https://confluence.atlassian.com/bitbucketserver/http-access-tokens-939515499.html). You will need to create an access token with "PROJECT\_READ" and "REPO\_ADMIN" values.

To connect Pipekit, click the button for BitBucket Data Center, input the access token and the URL to your BitBucket Data Center installation endpoint, then click "Submit".

### Azure DevOps

Azure DevOps Services (`dev.azure.com/{org}`) is supported via a Personal Access Token.

Create a PAT with these scopes: Code (Read, Write, & Status) and Project & Team (Read). The PAT owner must be a Project Administrator — or have the [Edit subscriptions](https://learn.microsoft.com/en-us/azure/devops/service-hooks/view-permission?view=azure-devops) project permission — so Pipekit can register [Service Hook](https://learn.microsoft.com/en-us/azure/devops/service-hooks/overview?view=azure-devops) subscriptions. There is no longer a standalone "Service Hooks" PAT scope; Microsoft has made `vso.hooks*` [private](https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth?view=azure-devops), so the project-level permission is the gating mechanism.

To connect Pipekit, click the button for Azure DevOps, fill in the organization URL and the PAT, then click "Submit". One Pipekit account corresponds to one Azure DevOps organization; multiple projects within the organization are surfaced in the repo picker grouped by project name.

See the [self-hosting guide](/self-hosting-pipekit/integrating-with-your-git-provider.md#azure-devops) for the operator-side configuration that ships with each Pipekit deployment.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pipekit.io/pipekit/organization/creating-orgs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.