> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acrity.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure providers

> Public guide for connecting GitHub, GitLab, Azure DevOps, Bitbucket, Jira, Linear, and ClickUp to Acrity.

Providers are connected through the Console using Connected Apps, Credentials, Connectors, and each repository detail page. The recommended path is Connected Apps whenever the provider offers one, because the Console can track authorization, status, and reauthorization for you.

Connecting a Connected App is an authorization handoff, not an app registration. Acrity publishes and manages the provider app (the GitHub App, the GitLab or Bitbucket OAuth app, the Azure DevOps app registration, and so on) per deployment. You never create an app, configure a callback URL, or grant individual API permissions yourself. You sign in on the provider, choose the account or organization, select the repositories the app may reach, and approve.

## Choose a connection method

Most providers connect through a Connected App. Use a manual credential or a local connector only when a Connected App does not fit.

```mermaid theme={null}
flowchart TD
    A[How should Acrity reach the provider?] --> B{Does the provider offer<br/>an official Connected App?}
    B -->|Yes| C[Connected App official<br/>Console &gt; Connected Apps]
    B -->|No| D{Is the VCS private or self-hosted<br/>with no public inbound access?}
    D -->|Yes| E[Local connector<br/>Console &gt; Connectors]
    D -->|No| F[Manual credential<br/>Console &gt; Credentials]
```

| Method            | Best when                                                                                                  | Where                    |
| ----------------- | ---------------------------------------------------------------------------------------------------------- | ------------------------ |
| Connected App     | The provider offers an official app or OAuth. Preferred for centralized authorization and reauthorization. | Console > Connected Apps |
| Manual credential | The use case needs a specific token, password, or app password.                                            | Console > Credentials    |
| Local connector   | The VCS is private, self-hosted, or must be reached from your own network.                                 | Console > Connectors     |

<Note>
  Credentials and Connectors require a Workspace admin (platform admins also have access). Roles are fixed capability sets defined by Acrity, so no other role can create or manage them. See [Credentials](/en/console/credentials) and [Connectors](/en/console/connectors).
</Note>

## Connect a provider

Pick the provider below. In every case the flow is the same: open Connected Apps, get redirected to the provider, choose the account or organization, select repositories, and approve. Acrity manages the underlying provider app for you.

<Tabs>
  <Tab title="GitHub">
    Use the GitHub App to connect GitHub Cloud accounts and organizations.

    <Steps>
      <Step title="Open Connected Apps">
        Go to `Console > Connected Apps` and choose the GitHub App.
      </Step>

      <Step title="Authorize on GitHub">
        Acrity redirects you to GitHub. Sign in if prompted.
      </Step>

      <Step title="Choose the account or organization">
        Select the personal account or organization where the app should be installed.
      </Step>

      <Step title="Select repositories">
        Choose all repositories or a specific subset the app may access. You grant access to the app Acrity already publishes—there is nothing to register.
      </Step>

      <Step title="Approve and return">
        Approve the requested access. GitHub returns you to the Console; confirm that the installation appears as active, then connect the target projects in `Console > Repositories`.
      </Step>
    </Steps>

    The GitHub App is registered and managed by Acrity per deployment. You never create the app or configure a callback URL.

    <Note>
      If Acrity is used as a merge gate, configure GitHub branch protection rules to require the check published by Acrity.
    </Note>
  </Tab>

  <Tab title="GitLab">
    Use GitLab OAuth for GitLab.com. For GitLab self-managed, provide the instance URL when prompted, or use a [local connector](/en/console/connectors) if the instance is on a private network.

    <Steps>
      <Step title="Open Connected Apps">
        Go to `Console > Connected Apps` and choose GitLab.
      </Step>

      <Step title="Enter the instance URL">
        For GitLab self-managed, enter the instance base URL when prompted. Skip this for GitLab.com.
      </Step>

      <Step title="Authorize on GitLab">
        Acrity redirects you to GitLab. Sign in and confirm the correct group or namespace.
      </Step>

      <Step title="Approve and connect">
        Approve the requested access, return to the Console, and connect the target projects in `Console > Repositories`.
      </Step>
    </Steps>

    The GitLab OAuth app is managed by Acrity. You only authorize access and select projects.
  </Tab>

  <Tab title="Azure DevOps">
    Connect Azure DevOps organizations through Microsoft sign-in.

    <Steps>
      <Step title="Open Connected Apps">
        Go to `Console > Connected Apps` and choose Azure DevOps.
      </Step>

      <Step title="Authorize with Microsoft">
        Acrity redirects you to Microsoft sign-in. Sign in with an account that can access the target organization.
      </Step>

      <Step title="Select the organization">
        Choose the Azure DevOps organization to connect.
      </Step>

      <Step title="Approve and connect">
        Approve the requested access, return to the Console, and connect the target repositories in `Console > Repositories`.
      </Step>
    </Steps>

    The Azure DevOps app registration is managed by Acrity. You do not create an app registration or configure a redirect URI.
  </Tab>

  <Tab title="Bitbucket">
    Connect Bitbucket Cloud workspaces through OAuth.

    <Tip>
      Bitbucket authorizes the account currently signed in to your browser. Sign in to Bitbucket with the correct account before you start.
    </Tip>

    <Steps>
      <Step title="Open Connected Apps">
        Go to `Console > Connected Apps` and choose Bitbucket.
      </Step>

      <Step title="Authorize on Bitbucket">
        Acrity redirects you to Bitbucket. Confirm the correct workspace.
      </Step>

      <Step title="Approve and connect">
        Approve the requested access, return to the Console, and connect the target repositories in `Console > Repositories`.
      </Step>
    </Steps>

    The Bitbucket OAuth consumer is managed by Acrity. You only authorize the workspace and select repositories.
  </Tab>

  <Tab title="Jira">
    Jira is a work management integration for PM fields, comments, and task linking.

    <Steps>
      <Step title="Open Connected Apps">
        Go to `Console > Connected Apps` and choose Jira.
      </Step>

      <Step title="Authorize on Atlassian">
        Acrity redirects you to Atlassian. Sign in and select the Jira site to connect.
      </Step>

      <Step title="Approve and link">
        Approve the requested access, return to the Console, and link the installation to repositories from the repository detail page.
      </Step>
    </Steps>

    The Jira OAuth app is managed by Acrity. Bitbucket and Jira are separate integrations, even when they belong to the same Atlassian organization.
  </Tab>

  <Tab title="Linear">
    Linear is a work management integration for issues and product context.

    <Steps>
      <Step title="Open Connected Apps">
        Go to `Console > Connected Apps` and choose Linear.
      </Step>

      <Step title="Authorize on Linear">
        Acrity redirects you to Linear. Sign in and approve the requested access.
      </Step>

      <Step title="Link to repositories">
        Return to the Console and link the Linear installation to existing repositories through the PM selector in the repository detail page.
      </Step>
    </Steps>

    The Linear OAuth app is managed by Acrity.
  </Tab>

  <Tab title="ClickUp">
    ClickUp is a work management integration for tasks and product context.

    <Steps>
      <Step title="Open Connected Apps">
        Go to `Console > Connected Apps` and choose ClickUp.
      </Step>

      <Step title="Authorize the workspaces">
        Acrity redirects you to ClickUp. Sign in and approve access for the required workspaces.
      </Step>

      <Step title="Link to repositories">
        Return to the Console and link the integration to repositories.
      </Step>
    </Steps>

    The ClickUp OAuth app is managed by Acrity. You only authorize the workspaces and link them to repositories.
  </Tab>
</Tabs>

## Validation checklist

After connecting a provider:

1. Confirm that the installation appears as active in `Console > Connected Apps`.
2. Connect at least one repository in `Console > Repositories`.
3. Open the repository detail page and validate credentials, webhook, and readiness.
4. If a PM integration is present, confirm task fields, comments, and project linking.
5. Open a test PR or MR and track the first review in the Ops dashboard (see [Review flow](/en/guides/review-flow)).