# Marketplace Apps - Managing External Connections

> Apps enable you to integrate GHL Customer Care with third-party applications. To achieve this integration, you must connect the app with the third-party…

- Source: https://docs.ghlcustomercare.com/docs/app-marketplace/workflow-triggers-and-actions/marketplace-apps-managing-external-connections
- Section: App marketplace / Workflow Triggers & Actions
- Reading time: 1 min
- Images: 2, each explained below
- Modified on Thu, 13 Feb, 2025 at 12:38 PM

---
Apps enable you to integrate GHL Customer Care with third-party applications. To achieve this integration, you must connect the app with the third-party application. This document explains how these connections work and are managed.

## **Understanding the basics**

-   All connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app
-   If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed.

![Understanding the basics (image 1 of 2)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155041573300/original/ik0HIVrKF1X-aTWH85LsiPS0QbNUWEzSbg.png)

**Understanding the basics (image 1 of 2)**

This screenshot appears in the "Understanding the basics" section of "Marketplace Apps - Managing External Connections". The text alongside this image reads: All connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed. Immediately after, the guide continues: If you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users….
- What this covers: All connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed.
- Next: If you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users must connect the app within the sub-account marketplace.

Full procedure:

1. All connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app
2. If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed.

-   If you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users must connect the app within the sub-account marketplace.

![Understanding the basics (image 2 of 2)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155041573285/original/luvTYLuiRFg9O81K_AxTOFbCYXBc3n3AGg.png)

**Understanding the basics (image 2 of 2)**

This screenshot appears in the "Understanding the basics" section of "Marketplace Apps - Managing External Connections". The text alongside this image reads: If you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users must connect the app within the sub-account marketplace. Immediately after, the guide continues: We currently support three types of authentication methods.
- What this covers: If you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users must connect the app within the sub-account marketplace.
- Next: We currently support three types of authentication methods:

Full procedure:

1. All connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app
2. If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed.

## **What authentication methods are supported?**

-   We currently support three types of authentication methods:
    -   OAuth - Login with third-party app and authorise the integration
    -   API Keys - Copy API key from the third-party app and paste it in GHL Customer Care
    -   Basic Auth - Username/Password credentials of your third party app

---

Documentation for GHL Customer Care. Support: support@ghlcustomercare.com