# Configure Organization Integrations Use the **Settings → Integrations** page to connect your organization to supported source control providers. These connections let Atloria work with your repositories and make provider-specific options available where needed. ## Overview Organization integrations connect Atloria to external repository systems. The available providers are **GitHub**, **GitLab**, and **Bitbucket**. Each provider appears as a separate integration option so you can connect only the systems your organization uses. You may need to configure an integration when you are setting up Atloria for the first time, when your organization adopts an additional source control provider, or when an existing connection needs to be checked or removed. A new organization may show the status **1. Fresh (No Connections)**. As connections are added, the interface can indicate states such as **2. GitHub Connected**, **2. Configured**, or **3. All Connected**. After a provider is connected, you can use **Test Connection** to confirm that Atloria can still communicate with the external system. You can also select **Disconnect** when an integration is no longer required. > 📷 _Screenshot pending: The Settings → Integrations page showing GitHub, GitLab, and Bitbucket connection options._ ## Prerequisites Before you begin, make sure that: - You can access your organization’s **Settings** area in Atloria. - You have the required permissions to manage organization integrations. - You have authorization to connect the relevant GitHub, GitLab, or Bitbucket account or organization. - You know which repositories or provider organization Atloria should be able to access. - Your browser allows the provider’s sign-in or authorization window to open, if prompted. ## Step-by-Step Instructions 1. Open **Settings → Integrations** from the Atloria application. 2. Review the available provider options for **GitHub**, **GitLab**, and **Bitbucket**. 3. Identify the provider you want to connect by checking its connection status. 4. Click **Connect Provider** for the provider you want to configure. 5. Click **Connect** to begin the provider connection process. 6. Complete the authorization prompts shown by the external provider. 7. Return to Atloria after the provider confirms the authorization. 8. Verify that the provider is no longer shown as not connected; Atloria may display a message such as “GitHub is not connected” before a successful connection is completed. 9. Confirm that the integration status changes to a connected or configured state, such as **2. GitHub Connected** or **2. Configured**. 10. Click **Test Connection** for the connected provider. 11. Review the test result to confirm that Atloria can communicate with the provider. 12. Click **Configure →** if additional configuration is available for that provider. 13. Select **Configure CI/CD** if you need to continue with continuous integration or continuous delivery setup for the connected provider. > 📷 _Screenshot pending: A connected provider card showing the Test Connection, Configure →, Configure CI/CD, and Disconnect actions._ ### Disconnect an integration Use these steps only when your organization no longer needs a provider connection. 1. Locate the connected provider on the **Settings → Integrations** page. 2. Click **Disconnect** for that provider. 3. Confirm the disconnection if Atloria asks you to confirm the action. 4. Verify that the provider returns to an unconnected status. Disconnecting removes the provider connection from Atloria. If projects or workflows rely on that provider, review their configuration before disconnecting it. ## Tips and Best Practices - Connect only the providers your organization actively uses. If your organization uses GitHub but not GitLab or Bitbucket, you can leave the unused providers disconnected. - Use **Test Connection** after the initial connection and whenever repository access stops working as expected. Testing the connection is the quickest way to verify that the saved integration is still available. - Check the status indicators before making changes. **1. Fresh (No Connections)** indicates that no providers are connected, while **3. All Connected** indicates that all available provider connections have been completed. - Use **Configure →** only after the provider is connected. Configuration options are most useful once Atloria can access the external provider. - If your team uses automated build or deployment workflows, select **Configure CI/CD** after establishing the source control connection. This keeps repository access and CI/CD setup aligned. - Avoid disconnecting a provider as a troubleshooting shortcut. First use **Test Connection** and verify that you are signed in to the correct external account. Disconnecting may require you to repeat the authorization process. - If you are connecting a repository during project setup, look for **Connect Your Repository** or **Manage in Settings**. These options direct you to the appropriate connection workflow or the organization integration settings. ## Related Pages - [Connect Your Repository](#) - [Configure CI/CD](#) - [Manage Projects and Repositories](#) - [Organization Settings](#) - [Events](#) ## Troubleshooting ### The provider is still shown as not connected Click **Connect Provider**, then select **Connect** again. Complete every authorization prompt from the external provider before returning to Atloria. If the status does not change, confirm that you authorized the correct provider account or organization. ### The connection test does not succeed Click **Test Connection** again after confirming that your external provider account is active and that you still have access to the intended repositories. If the test continues to fail, disconnect the provider only if you are prepared to authorize it again, then reconnect it. ### You cannot find configuration options First confirm that the provider shows a connected status, such as **2. Configured** or **2. GitHub Connected**. After the connection is active, use **Configure →** or **Configure CI/CD** when those actions are available.