GoHighLevel
Connect GoHighLevel to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect GoHighLevel to collect crm evidence with automated compliance tests, switched on per workspace.
| Category | CRM |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| GoHighLevel's guide | marketplace.gohighlevel.com |
Connect with an API token
-
In GoHighLevel:
- Sign in to HighLevel as an agency admin and open Private Integrations under agency settings (if you don't see it, enable the feature on Labs).
- Click Create new Integration.
- Give the Private Integration a name and description.
- Select the scopes/permissions the private integration should have; Safeguard only needs read access to users.
- Copy the generated token right away (you won't be able to copy it again later) and paste it into Private integration token.
Where to find the other values:
- Company ID (optional): Not shown in the fetched HighLevel article; leave empty unless you know your agency (company) ID.
- Location ID (optional): The sub-account ID; the fetched article does not say where the UI shows it.
GoHighLevel shows the secret only once, so copy it before you leave the page.
GoHighLevel's public documentation does not cover every step.
By default all agency admins can create Private Integrations; access can be restricted under Settings > Team > Roles & Permissions. Limit of 20 tokens at Agency level and 20 per Location. The exact settings menu path to the Private Integrations page and the locations of Company ID and Location ID were not in the fetched article. Verification: the fetched article names no scope identifiers, so the users.readonly scope name was removed, and it does not give the sub-account (Location-level) path.
Source: help.gohighlevel.com, checked 2026-10-07.
The permissions Safeguard needs:
users.readonly. -
On Compliance › Connectors, open GoHighLevel, click Connect, choose API token and fill in:
Field What to enter Private integration token Optional. Stored encrypted and never shown again. Company ID (optional) — Or, instead: Location ID (optional).
-
Click Connect with token.
Frameworks
Safeguard's automated tests read GoHighLevel and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC6.2, CC6.3 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 3 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- CRM connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks