---
title: "Configure connections"
canonical: "https://support.appfire.com/space/RS/3159457879/Configure%20connections"
format: markdown
---
> Macro (aura-html)

Use the **Connections** page to connect Appfire QueueZero to Atlassian, GitHub, and Bitbucket.

QueueZero uses these connections to access Jira work items, Confluence documentation, repositories, and pull request workflows.

You can also configure organization-level private package registries for repositories that require private dependencies during Env Grounding.

## Before you begin

Make sure you have:

- Organization admin or owner access in QueueZero.
- Permission to authorize the tools you want to connect.
- Access to the Jira sites, Confluence spaces, repositories, or workspaces your teams will use.

## Add connections

1. Open the QueueZero standalone app.
2. From the side menu, select **Connections**.
3. Connect the providers your organization uses.

![Configure organization connections in Appfire QueueZero](media://06aa5f22-add9-4cf1-827c-108d37a13d91)

### Connect Atlassian

Connect Atlassian so QueueZero can access Jira work items and Confluence documentation.

QueueZero connects to Atlassian using OAuth. Atlassian API keys are not supported.

1. On the **Atlassian** card, select **Connect with Atlassian**.
2. Follow the Atlassian authorization flow.
3. Select the Atlassian site or sites QueueZero should access.
4. Click **Connect site**.

After the connection is complete, confirm that the expected Jira sites are listed on the Atlassian connection.

### Connect GitHub

Connect GitHub so QueueZero can access GitHub repositories and create pull requests.

1. On the **GitHub** card, click **Connect with Github**.
2. Follow the GitHub authorization flow.
3. Choose whether to give QueueZero access to all repositories or only selected repositories.
4. Click **Install & Authorize**.
5. Complete any additional authorization steps shown by GitHub.

### Connect Bitbucket

Connect Bitbucket so QueueZero can access Bitbucket repositories and pull request workflows.

1. On the **Bitbucket** card, click **Connect with Bitbucket**.
2. Follow the Bitbucket authorization flow.

The Bitbucket connection uses your Atlassian credentials. If you have already authorized the required Atlassian account, you may not need to sign in again.

## Configure private package registries

Use **Organization registries** to provide QueueZero with credentials for private package registries such as Nexus or Artifactory.

Private registry connections are organization-wide and can be used when Env Grounding needs to install dependencies that are not available from public registries.

To add a registry:

1. On the **Connections** page, find **Organization registries**.
2. Select **Add registry**.
3. Enter a name for the connection.
4. Enter the HTTPS registry URL.
5. Optionally, specify the package scopes that should use the registry.
6. Select the provider and package ecosystem.
7. Provide either:
  - an access token, or
  - a username and password.
8. Select **Test & save**.

QueueZero tests the registry connection before saving it.

If you specify package scopes, only matching packages use the registry. If you leave the scopes empty, the registry can be used for all packages for the selected ecosystem.

When possible, use a read-only service account or token for registry access.

Stored credentials are not displayed again. If you edit a registry connection, you may need to enter the credentials again.

For information about using a private registry during environment setup, see **[Set up Env Grounding](https://appfire.atlassian.net/wiki/spaces/RS/pages/3624304708)**.

## Review connection status

After adding a connection, return to the **Connections** page and check that the provider card shows **Connected**.

Also confirm that the expected sites, organizations, repositories, or workspaces are available.

If a connection is missing, awaiting approval, or disconnected, complete the required action with the provider before using it in a QueueZero space.

## Connection actions

Available actions depend on the provider.

From the provider card, click **Manage** to review the connection and available actions. Depending on the provider, you may be able to:

- Connect another account.
- Change which resources QueueZero can access.
- Update access through the provider.
- Remove the connection from QueueZero.

Removing a connection can affect QueueZero spaces that depend on its Jira sites, documentation sources, repositories, or pull request workflows.

## Next step

After connecting the required tools, create or open a QueueZero space and configure the context QueueZero should use.

For more information, see:

- **[Create a QueueZero space](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932)**
- **[Map Jira spaces to QueueZero spaces](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932/Set+up+spaces#Step-2%3A-Map-Jira-spaces)**
- **[Add repositories and documentation sources](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932/Set+up+spaces#Step-3%3A-Set-up-space-knowledge)**