# Private Integrations: Everything you need to know

> Learn how GHL Customer Care Private Integrations work, how to create secure API tokens, manage scopes, rotate tokens, and connect custom integrations.

- Source: https://docs.ghlcustomercare.com/docs/integrations/private-integrations/private-integrations-everything-you-need-to-know
- Section: Integrations / Private Integrations
- Reading time: 6 min
- Images: 19, each explained below
- Modified on Wed, 24 Jun at 10:39 PM

---
## 

Private Integrations allow you to build secure, custom connections between your GHL Customer Care account and any third-party application. This feature is ideal for internal tools, automated workflows, and custom systems that need API access without building a full public app.

**IMPORTANT**: For a full list of available endpoints and request/response details, visit our official API documentation: https://marketplace.https://ghlcustomercare.com/docs/

---

[](https://docs.ghlcustomercare.com/docs/integrations/private-integrations/private-integrations-everything-you-need-to-know)

---

**TABLE OF CONTENTS**

-   [What are Private Integrations?](#what-are-private-integrations)
-   [What's the difference between Private Integrations and API Keys?](#whats-the-difference-between-private-integrations-and-api-keys)
-   [What's the difference between Private Integrations and OAuth2 Access Tokens?](#whats-the-difference-between-private-integrations-and-oauth2-access-tokens)
-   [How do I use Private Integrations?](#how-do-i-use-private-integrations)
-   [Testing a Private Integration with API Calls](#testing-a-private-integration-with-api-calls)
-   [How do I manage Private Integrations?](#how-do-i-manage-private-integrations)
-   [Where can I find Private Integrations?](#where-can-i-find-private-integrations)
-   [How do I create a new Private Integration?](#how-do-i-create-a-new-private-integration)
-   [What are some best practices to maintain the security of my private integration token?](#what-are-some-best-practices-to-maintain-the-security-of-my-private-integration)
-   [Token compromised?](#token-compromised)
-   [Can I edit the Private Integration permissions without updating the token?](#can-i-edit-the-private-integration-permissions-without-updating-the-token)
-   [How do I delete the Private Integration once I no longer need it?](#how-do-i-delete-the-private-integration-once-i-no-longer-need-it)

---

## **What are Private Integrations?**

Private Integrations allows you to build powerful custom integrations between your GHL Customer Care account and any other third-party app.

If you are looking to integrate your GHL Customer Care account with a third-party app, you have two options:

-   Find and install the relevant app from the App Marketplace
-   Build your own private integration by yourself or with the help of a developer using APIs.

Private Integrations helps you achieve #2 securely.

The key advantages of using Private Integrations are:

-   Simple: Generate Private Integration tokens from your account settings and manage them with ease.
-   Secure: You get to restrict the scopes/permissions that a developer can access on your account

Private Integrations are available for both Agencies and Sub-Accounts. To know more about the sub-accounts' Private Integrations feature, click here.

---

## **What's the difference between Private Integrations and API Keys?**

Private Integrations, to put it simply, is more powerful yet secure alternative to API Keys.

<table style="width: 100%"><tbody><tr><td dir="ltr" style="width: 50%"><div style="text-align: center"><strong dir="ltr"><span dir="ltr">Private Integrations</span></strong></div></td><td dir="ltr" style="width: 50%"><div style="text-align: center"><strong dir="ltr"><span dir="ltr">API Keys</span></strong></div></td></tr><tr><td dir="ltr" style="width: 50.0000%"><strong dir="ltr">More Secure</strong>: You get to restrict the scopes/permissions that a developer can access on your account&nbsp;</td><td dir="ltr" style="width: 50.0000%"><strong dir="ltr">Less Secure</strong>: A developer gets unrestricted access to all your account data&nbsp;</td></tr><tr><td dir="ltr" style="width: 50.0000%"><strong dir="ltr">State-of-the-art</strong>: <span dir="ltr" style="font-weight: 400; text-align: left">Private Integrations allows you to access API v2.0, which is state of the art.</span></td><td dir="ltr" style="width: 50.0000%"><strong>Outdated</strong>: API Keys work on API v1.0, which has reached end-of-life and is no longer maintained.</td></tr><tr><td dir="ltr" style="width: 50.0000%"><strong dir="ltr">More Features:&nbsp;</strong>API v2.0 has more powerful APIs</td><td dir="ltr" style="width: 50.0000%"><strong dir="ltr">Fewer Features</strong>: API v1.0 has limited APIs</td></tr></tbody></table>

---

## **Why Private Integration Tokens Are Recommended for New Credentials**

Private Integration Tokens (PIT) are the recommended replacement for legacy API keys because they provide more secure and flexible access management.

Legacy API keys that remain unused for more than 90 days may be marked as Expired in settings. Because new legacy v1 key creation is no longer supported, PIT should be used for any new credentials or when migrating older integrations to a more secure access model.

If you still rely on a legacy API key, GHL Customer Care recommends moving that integration to a Private Integration Token whenever possible.

![Why Private Integration Tokens Are Recommended for New Credentials (image 1 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155074448956/original/hHvWuKsdPjwkb3-fw9OW4-w0zwINy_iZsA.png)

**Why Private Integration Tokens Are Recommended for New Credentials (image 1 of 19)**

This screenshot appears in the "Why Private Integration Tokens Are Recommended for New Credentials" section of "Private Integrations: Everything you need to know". The text alongside this image reads: If you still rely on a legacy API key, GHL Customer Care recommends moving that integration to a Private Integration Token whenever possible. Immediately after, the guide continues: Private Integrations, to put it simply, is static/fixed OAuth2 Access Tokens.
- What this covers: If you still rely on a legacy API key, GHL Customer Care recommends moving that integration to a Private Integration Token whenever possible.
- Next: Private Integrations, to put it simply, is static/fixed OAuth2 Access Tokens.

---

## **What's the difference between Private Integrations and OAuth2 Access Tokens?**

Private Integrations, to put it simply, is static/fixed OAuth2 Access Tokens.

<table style="max-width: 100%; font-weight: 400; text-align: left; width: 718px"><tbody><tr><td dir="ltr" style="min-width: 5px; width: 358.5px"><div style="text-align: center"><strong dir="ltr" style="font-weight: 700"><span dir="ltr">Private Integrations</span></strong></div></td><td dir="ltr" style="min-width: 5px; width: 358.5px"><div style="text-align: center"><strong dir="ltr" style="font-weight: 700"><span dir="ltr">Access Tokens</span></strong></div></td></tr><tr><td dir="ltr" style="min-width: 5px; width: 358.5px"><strong dir="ltr" style="font-weight: 700">Generated from the UI</strong>: The Private Integration token can be generated easily from the UI.</td><td dir="ltr" style="min-width: 5px; width: 358.5px"><strong dir="ltr" style="font-weight: 700">Programmatic Generation</strong>: API Tokens are generated by exchanging an OAuth access code for the tokens using Get Access Token API.</td></tr><tr><td dir="ltr" style="min-width: 5px; width: 358.5px"><strong dir="ltr" style="font-weight: 700">Static/Fixed</strong>: Private Integration Tokens are static/fixed and do not automatically refresh unless you rotate them from the UI.</td><td dir="ltr" style="min-width: 5px; width: 358.5px"><strong dir="ltr" style="font-weight: 700">Refreshed Daily</strong>: Access Tokens expire daily and need to be refreshed.</td></tr></tbody></table>

---

## **How do I use Private Integrations?**

Private Integration tokens are used in the Authorisation header, just like other Access Tokens.

For example, to get a location's details, you can use Get Sub-account API with the Agency's Private Integration Token in the Authorisation header.

curl --request GET \\
  --url https://services.leadconnectorhq.com/locations/ve9EPM428h8vShlRW1KT \\
  --header 'Accept: application/json' \\
  --header 'Authorization: <YOUR PRIVATE INTEGRATION TOKEN>' \\
  --header 'Version: 2021-07-28'

---

## **Testing a Private Integration with API Calls**

Once your Private Integration is created, you may want to test it by pushing data to an API endpoint. you will need the correct API endpoint URL to do this.

Here’s an example of how to test the integration by adding a new contact:

curl --request POST \\
  --url https://services.leadconnectorhq.com/contacts/ \\
  --header 'Authorization: <YOUR PRIVATE INTEGRATION TOKEN>' \\
  --header 'Content-Type: application/json' \\
  --header 'Version: 2021-07-28' \\
  --data '{
    "firstName": "John",
    "lastName": "Doe",
    "email": "john.doe@example.com",
    "phone": "+1234567890",
    "locationId": "LOCATION\_ID"
  }'

Make sure to:

-   Replace LOCATION\_ID with the actual sub-account ID.
-   Replace Authorization value with your generated Private Integration token.

For a full list of available endpoints and testing capabilities, visit our official developer documentation: https://developers.https://ghlcustomercare.com

---

## **How do I manage Private Integrations?**

### **Who can create Private Integrations?**

By default, all agency admins can create and manage Private Integrations. 

However, you can restrict this permission at a user level. To do this, Navigate to Settings > Team > Edit the specific agency admin > Roles & Permissions, and enable/disable Private Integrations for the agency admin.

You may apply the restrictions at two levels:

1.  Allow the agency admin to view and manage the agency's private integrations
2.  Allow the agency admin to view and manage the sub-accounts' private integrations

### 

![Who can create Private Integrations? (image 2 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155030659842/original/6lOsxQuiq4N2bHX6ewlVrmDuEAnUy9QDpQ.png)

**Who can create Private Integrations? (image 2 of 19)**

This screenshot appears in the "Who can create Private Integrations?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Allow the agency admin to view and manage the agency's private integrations Allow the agency admin to view and manage the sub-accounts' private integrations. Immediately after, the guide continues: You can find Private Integrations under agency settings. If you don't find it under settings, please make sure that you have enabled the feature on Labs.
- What this covers: Allow the agency admin to view and manage the agency's private integrations Allow the agency admin to view and manage the sub-accounts' private integrations
- Next: You can find Private Integrations under agency settings. If you don't find it under settings, please make sure that you have enabled the feature on Labs.

---

## **Where can I find Private Integrations?**

You can find Private Integrations under agency settings. If you don't find it under settings, please make sure that you have enabled the feature on Labs.

![Where can I find Private Integrations? (image 3 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155030660190/original/wGql6-BrqjOpzKCG65lxrkC9FH-3G8CjaQ.png)

**Where can I find Private Integrations? (image 3 of 19)**

This screenshot appears in the "Where can I find Private Integrations?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: You can find Private Integrations under agency settings. If you don't find it under settings, please make sure that you have enabled the feature on Labs. Immediately after, the guide continues: Step 1: Click on "Create new Integration".
- What this covers: You can find Private Integrations under agency settings. If you don't find it under settings, please make sure that you have enabled the feature on Labs.
- Next: Step 1: Click on "Create new Integration"

---

## **How do I create a new Private Integration?**

**Step 1:** Click on "Create new Integration"

![How do I create a new Private Integration? (image 4 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029013962/original/yvAW6A_NW5gJMcSx395zGtXk6qkFXs3o5A.png)

**How do I create a new Private Integration? (image 4 of 19)**

This screenshot appears in the "How do I create a new Private Integration?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 1: Click on "Create new Integration". Immediately after, the guide continues: Step 2: Give your Private Integration a name and description to help you and your team identify what it's for.
- What to click: Step 1: Click on "Create new Integration"
- Next: Step 2: Give your Private Integration a name and description to help you and your team identify what it's for.

**Step 2:** Give your Private Integration a name and description to help you and your team identify what it's for.

![How do I create a new Private Integration? (image 5 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029014111/original/ZPgWRbFa4SBbD-MteF42NGBCtFc_Web7EA.png)

**How do I create a new Private Integration? (image 5 of 19)**

This screenshot appears in the "How do I create a new Private Integration?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 2: Give your Private Integration a name and description to help you and your team identify what it's for. Immediately after, the guide continues: Step 3: Select the scopes/permissions that you want the private integration to have access to on your agency account. Ensure that you are selecting only the required scopes for better data security.
- What this covers: Step 2: Give your Private Integration a name and description to help you and your team identify what it's for.
- Next: Step 3: Select the scopes/permissions that you want the private integration to have access to on your agency account. Ensure that you are selecting only the required scopes for better data security.

**Step 3:** Select the scopes/permissions that you want the private integration to have access to on your agency account. Ensure that you are selecting only the required scopes for better data security.

![How do I create a new Private Integration? (image 6 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155030660243/original/EefivfaL6w17chXrSdbaMXTnd9oQs26hNg.png)

**How do I create a new Private Integration? (image 6 of 19)**

This screenshot appears in the "How do I create a new Private Integration?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 3: Select the scopes/permissions that you want the private integration to have access to on your agency account. Ensure that you are selecting only the required scopes for better data security. Immediately after, the guide continues: Step 4: Copy the token generated and share it with your third-party app developer.
- What to choose: Step 3: Select the scopes/permissions that you want the private integration to have access to on your agency account. Ensure that you are selecting only the required scopes for better data security.
- Next: Step 4: Copy the token generated and share it with your third-party app developer.

**Step 4:** Copy the token generated and share it with your third-party app developer. 

Please ensure that you are sharing the token with trusted parties only. Do not share it publicly.

**Note:** Don't forget to copy the token generated as you won't be able to do it again later.

![How do I create a new Private Integration? (image 7 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029056315/original/iDIuSpkuzyH_p2OdR30IDSvLE7CxS05gQQ.png)

**How do I create a new Private Integration? (image 7 of 19)**

This screenshot appears in the "How do I create a new Private Integration?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Note: Don't forget to copy the token generated as you won't be able to do it again later. Immediately after, the guide continues: We recommend that you rotate your Private Integration tokens every 90 days.
- What to copy: Note: Don't forget to copy the token generated as you won't be able to do it again later.
- Next: We recommend that you rotate your Private Integration tokens every 90 days.

---

## **What are some best practices to maintain the security of my private integration token?**

We recommend that you rotate your Private Integration tokens every 90 days.

Here's how you can do it.

###   

**Step 1:** Navigate to Private Integrations under settings, and click on the Private Integration you have created.

![What are some best practices to maintain the security of my private integration token? (image 8 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029015449/original/YI9nMQbgJqStpF_RBJKBUdj46z9WudaC1g.png)

**What are some best practices to maintain the security of my private integration token? (image 8 of 19)**

This screenshot appears in the "What are some best practices to maintain the security of my private integration token?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 1: Navigate to Private Integrations under settings, and click on the Private Integration you have created. Immediately after, the guide continues: Step 2: Click on "Rotate and expire this token later".
- What to click: Step 1: Navigate to Private Integrations under settings, and click on the Private Integration you have created.
- Next: Step 2: Click on "Rotate and expire this token later".

Full procedure:

1. "Cancel rotation" if, for example, your developer needs more time to update the token on the third-party app.
2. "Expire Now", if, for example, the third-party app has been updated with the new token.

**Step 2:** Click on "Rotate and expire this token later".

![What are some best practices to maintain the security of my private integration token? (image 9 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029055790/original/jZAec5alCqx2g3Mz7J4HCW1gpw2dzTHFTQ.png)

**What are some best practices to maintain the security of my private integration token? (image 9 of 19)**

This screenshot appears in the "What are some best practices to maintain the security of my private integration token?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 2: Click on "Rotate and expire this token later". Immediately after, the guide continues: Step 3: Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation.
- What to click: Step 2: Click on "Rotate and expire this token later".
- Next: Step 3: Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation.

Full procedure:

1. "Cancel rotation" if, for example, your developer needs more time to update the token on the third-party app.
2. "Expire Now", if, for example, the third-party app has been updated with the new token.

**Step 3:** Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation.

![What are some best practices to maintain the security of my private integration token? (image 10 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029055827/original/M40HLVVe3lBbA0BQ5UX-27DLtKK4PbJOkw.png)

**What are some best practices to maintain the security of my private integration token? (image 10 of 19)**

This screenshot appears in the "What are some best practices to maintain the security of my private integration token?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 3: Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation. Immediately after, the guide continues: Step 4: Copy the new token and update it on your third-party app.
- What to click: Step 3: Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation.
- Next: Step 4: Copy the new token and update it on your third-party app.

Full procedure:

1. "Cancel rotation" if, for example, your developer needs more time to update the token on the third-party app.
2. "Expire Now", if, for example, the third-party app has been updated with the new token.

**Step 4:** **Copy the new token and update it on your third-party app.** 

You will have a 7-day window where both the old and the new tokens will continue to work. After 7 days, the old token will expire. In this 7-day window, you will have the option to:

-   "Cancel rotation" if, for example, your developer needs more time to update the token on the third-party app.
-   "Expire Now", if, for example, the third-party app has been updated with the new token.

**Note:** Don't forget to copy the token generated as you won't be able to do it again later. 

![What are some best practices to maintain the security of my private integration token? (image 11 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029055978/original/cs7V4-owR-cA74RwmVmxGDPnAAoecXYpwg.png)

**What are some best practices to maintain the security of my private integration token? (image 11 of 19)**

This screenshot appears in the "What are some best practices to maintain the security of my private integration token?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Note: Don't forget to copy the token generated as you won't be able to do it again later. Immediately after, the guide continues: Step 1: Navigate to Private Integrations under settings, and click on the Private Integration you have created.
- What to copy: Note: Don't forget to copy the token generated as you won't be able to do it again later.
- Next: Step 1: Navigate to Private Integrations under settings, and click on the Private Integration you have created.

Full procedure:

1. "Cancel rotation" if, for example, your developer needs more time to update the token on the third-party app.
2. "Expire Now", if, for example, the third-party app has been updated with the new token.

---

## **Token compromised?**

**Step 1: Navigate to Private Integrations under settings, and click on the Private Integration you have created.**

![Token compromised? (image 12 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029015449/original/YI9nMQbgJqStpF_RBJKBUdj46z9WudaC1g.png)

**Token compromised? (image 12 of 19)**

This screenshot appears in the "Token compromised?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 1: Navigate to Private Integrations under settings, and click on the Private Integration you have created. Immediately after, the guide continues: Step 2: Click on "Rotate and expire this token now".
- What to click: Step 1: Navigate to Private Integrations under settings, and click on the Private Integration you have created.
- Next: Step 2: Click on "Rotate and expire this token now".

**Step 2: Click on "Rotate and expire this token now".**

![Token compromised? (image 13 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029056233/original/1CO8ADONFx1V4l2rZnWDSVNrd5t8mM2NgQ.png)

**Token compromised? (image 13 of 19)**

This screenshot appears in the "Token compromised?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 2: Click on "Rotate and expire this token now". Immediately after, the guide continues: Step 3: Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation.
- What to click: Step 2: Click on "Rotate and expire this token now".
- Next: Step 3: Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation.

**Step 3: Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation.** 

![Token compromised? (image 14 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029056251/original/OKlV-5OLCEpFvIO_Ku-xOShU5kLoOKQGRg.png)

**Token compromised? (image 14 of 19)**

This screenshot appears in the "Token compromised?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 3: Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation. Immediately after, the guide continues: Step 4: Copy the new token and update it on your third-party app.
- What to click: Step 3: Click "Continue" in response to the warning message if you are sure that you want to proceed with rotation.
- Next: Step 4: Copy the new token and update it on your third-party app.

Step 4: Copy the new token and update it on your third-party app.

**Note:** Don't forget to copy the token generated as you won't be able to do it again later.

![Token compromised? (image 15 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029056314/original/qTmiWdCADNy02lzHwiGrcrfcOs-HAQIL2w.png)

**Token compromised? (image 15 of 19)**

This screenshot appears in the "Token compromised?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Note: Don't forget to copy the token generated as you won't be able to do it again later. Immediately after, the guide continues: Yes, you can edit the Private Integration name, description and scopes/permissions any time after you've created it.
- What to copy: Note: Don't forget to copy the token generated as you won't be able to do it again later.
- Next: Yes, you can edit the Private Integration name, description and scopes/permissions any time after you've created it.

---

## **Can I edit the Private Integration permissions without updating the token?**

Yes, you can edit the Private Integration name, description and scopes/permissions any time after you've created it.

Here's how you can do it.

**Step 1: Navigate to Private Integrations under settings, and select "Edit" from the three-dot menu.**

![Can I edit the Private Integration permissions without updating the token? (image 16 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029056506/original/g5TVdfhF6e56Uj9eU3F-f8MDjhINdvwySQ.png)

**Can I edit the Private Integration permissions without updating the token? (image 16 of 19)**

This screenshot appears in the "Can I edit the Private Integration permissions without updating the token?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 1: Navigate to Private Integrations under settings, and select "Edit" from the three-dot menu. Immediately after, the guide continues: Step 2: Update the Private Integration name and description if required. Click on "Next".
- What to choose: Step 1: Navigate to Private Integrations under settings, and select "Edit" from the three-dot menu.
- Controls: 5 Private Integration Tokens (PIT), Agency level, Location level, Note
- Next: Step 2: Update the Private Integration name and description if required. Click on "Next".

**Step 2: Update the Private Integration name and description if required. Click on "Next".**

![Can I edit the Private Integration permissions without updating the token? (image 17 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029056523/original/QUgMnaLVazAjL3yWgsZGd5ruujrP6WQgUg.png)

**Can I edit the Private Integration permissions without updating the token? (image 17 of 19)**

This screenshot appears in the "Can I edit the Private Integration permissions without updating the token?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Step 2: Update the Private Integration name and description if required. Click on "Next". Immediately after, the guide continues: Step 3: If required, update the scopes/permissions that you want the private integration to have access to on your account.
- What to click: Step 2: Update the Private Integration name and description if required. Click on "Next".
- Controls: 5 Private Integration Tokens (PIT), Agency level, Location level, Note
- Next: Step 3: If required, update the scopes/permissions that you want the private integration to have access to on your account.

**Step 3: If required, update the scopes/permissions that you want the private integration to have access to on your account.** 

Ensure that you are selecting only the required scopes for better data security. Click on "Update" to save the updates made.

![Can I edit the Private Integration permissions without updating the token? (image 18 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029056555/original/-CYsioGb7fLRhBOW-4IaGpOmbrFmYWTp3Q.png)

**Can I edit the Private Integration permissions without updating the token? (image 18 of 19)**

This screenshot appears in the "Can I edit the Private Integration permissions without updating the token?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: Ensure that you are selecting only the required scopes for better data security. Click on "Update" to save the updates made. Immediately after, the guide continues: Users can create up to 5 Private Integration Tokens (PIT) at both the Agency level and the Location level.
- How to confirm: Ensure that you are selecting only the required scopes for better data security. Click on "Update" to save the updates made.
- Controls: 5 Private Integration Tokens (PIT), Agency level, Location level, Note
- Next: Users can create up to 5 Private Integration Tokens (PIT) at both the Agency level and the Location level.

Users can create up to **5 Private Integration Tokens (PIT)** at both the **Agency level** and the **Location level**.

**Note**: Updating the Private Integration details does not generate a new token. The existing token will continue to work.

---

## **How do I delete the Private Integration once I no longer need it?**

You can delete the Private Integration once you no longer use the third-party app. To do so, navigate to Private Integrations under settings, and select "Delete" from the three-dot menu.

![How do I delete the Private Integration once I no longer need it? (image 19 of 19)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155029056627/original/_JO1Og2ifY43mlxGgIYT1HGFpwUtB445eA.png)

**How do I delete the Private Integration once I no longer need it? (image 19 of 19)**

This screenshot appears in the "How do I delete the Private Integration once I no longer need it?" section of "Private Integrations: Everything you need to know". The text alongside this image reads: You can delete the Private Integration once you no longer use the third-party app. To do so, navigate to Private Integrations under settings, and select "Delete" from the three-dot menu.
- What to choose: You can delete the Private Integration once you no longer use the third-party app. To do so, navigate to Private Integrations under settings, and select "Delete" from the three-dot menu.

---

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