Skip to content

HighLevel permissions

For the HighLevel connector to work correctly in LightLead, certain access permissions in the CRM system are required.

Required permissions

An API key of type Location user is required. Rights: read opportunities, contacts, pipelines, custom fields. Binding to a specific location_id is mandatory.

Permission check

LightLead automatically checks access permissions during initial discovery. If any permissions are missing, you will see a corresponding warning in the interface.

Detailed list of permissions

PermissionDescriptionRequirement
Read entitiesAccess to the list and content of deals/orders/leadsRequired
Read pipelinesAccess to the list of pipelines and statusesRequired
Read usersAccess to the list of users/managersRecommended
Read custom fieldsAccess to custom field settings and valuesRecommended
Read contacts/companiesAccess to related contacts and companiesRecommended

Permission limitations

Some operations may be unavailable if certain permissions are missing:

  • Without pipeline permissions: reports grouped by pipeline and status are unavailable

  • Without user permissions: grouping by manager is unavailable

  • Without custom field permissions: custom fields are unavailable in filters and reports

  • Without contact permissions: attribution by contact data is unavailable

Updating permissions

If you changed access permissions in the CRM system, run discovery again in LightLead:

  1. Go to the connection settings

  2. Click Reconnect or Refresh discovery

  3. Wait for the permission check to complete

Maintained by the LightLead Documentation Team · Last verified: 2026-07-25