HighLevel integration

Connect authorized accounts with clear access boundaries.

Agency Dash Pro supports direct connected-account installation and an agency-owner authorization flow. New direct installs are enabled in the private pilot; bulk and future-location provisioning remain gated.

How connection and revocation work.

Customers can connect an authorized account by entering a read-only PIT in the client workspace or through the authorized OAuth path. The application encrypts credentials before storage. Refresh credentials are renewed by the server-side integration path; provider credentials are not returned to the browser.

Authorized source managers can permanently disconnect a source. The action invalidates its embed and removes the credential, cached reporting data, historical cursors, jobs, usage rows, related source-level settings, and CRM Defense progress. A disconnected embed cannot continue to display the account’s data.

OAuth permissions

Every requested scope has a reporting or authorization purpose.

Scope	Plain-language purpose
`locations.readonly`	Identify and validate an authorized connected account.
`locations/tags.readonly`	Read location tag configuration used in reporting.
`contacts.readonly`	Read contacts for aggregated reporting.
`opportunities.readonly`	Read pipeline and opportunity reporting.
`calendars.readonly`	Read calendar definitions used to interpret appointment reporting.
`calendars/events.readonly`	Read appointment events for reporting.
`conversations.readonly`	Read conversation metadata for reporting.
`conversations/message.readonly`	Read message-export metadata for reporting.
`users.readonly`	Read user references used in reporting.
`oauth.readonly`	Read authorization state.
`oauth.write`	Only exchange an authorized Company token for a child Location token; never edit CRM records.

Important integration note

Agency Dash Pro is an independent application and is not affiliated with or endorsed by HighLevel.

Agency Dash Pro requests no CRM-record write permissions. The narrow oauth.write permission is used only for authorized company-to-location token exchange.

Questions, answered

Practical answers before you connect.

Does Agency Dash Pro update dashboards in real time?

No. Connected-account data is refreshed through a managed queue. Core reporting data is scheduled frequently, while some historical or provider-limited data is reconciled on a longer cadence.

What counts as an account?

One active connected HighLevel client account or location counts as one account. Reusing the same dashboard embed does not create another charge.

Can I disconnect an account?

Yes. Authorized source managers can permanently disconnect a source. This invalidates its embed and removes the encrypted credential, cached reporting data, source-specific settings, and related sync state.

Does Agency Dash Pro write to CRM records?

No CRM-record write permissions are requested. The narrow oauth.write permission is used only for an authorized company-to-location token exchange.

Ready when your next client is

Give reporting a clear, repeatable home.

Start with one connected account, explore the templates, or tell us how you deliver client reporting today.

Start free Explore examples Contact sales