GridLane is designed to work inside the access an agency already grants. It does not create HighLevel users, bypass HighLevel permissions, or copy client records into a blueprint.
OAuth and access
GridLane connects through HighLevel OAuth. During installation, HighLevel shows the scopes GridLane requests. The app uses those scopes to read the selected objects and records, edit records, create fields, manage associations, and support the agency console.
OAuth tokens are encrypted before storage. Access tokens are refreshed before expiry when a refresh token is available. You can revoke access by uninstalling GridLane from HighLevel.
Company-scoped access
Agency routes are tied to the installing company. GridLane checks that a location belongs to the company before using a location token or returning agency data. A guessed location ID should not grant access to another company’s account.
HighLevel remains responsible for its own user roles and record-level permissions. GridLane’s permission rules are an additional app-level layer for grids, boards, views, and fields; they do not replace HighLevel’s security model.
What blueprints contain
Blueprints contain configuration:
- Objects and labels
- Fields, field settings, and required flags
- Sections and field placement
- Association definitions
- Saved GridLane grid and board views
- GridLane permission rules
Blueprints do not contain record values, conversations, appointments, or customer history.
What is stored in the app database
GridLane stores the configuration and operational data needed to run the agency console:
- Install records and encrypted OAuth credentials
- Saved grid and board views, layouts, and permission rules
- Blueprint versions and rollout jobs
- Drift results and agency metrics
- Audit events and reporting snapshots
- Plan and entitlement status
The app may cache HighLevel API responses for a short time to improve performance.
Audit history
Agency-level actions such as blueprint capture, rollout, drift checks, settings changes, tag edits, branding changes, and plan refreshes are recorded in the audit log. Audit detail is configuration-level; it does not include record values.
Enterprise plans can review and export the audit log. See Reporting and audit.
Encryption and infrastructure
GridLane runs on Cloudflare Workers with a managed PostgreSQL database. HighLevel data is requested through the HighLevel API. Secrets such as OAuth credentials and encryption keys are stored as Worker secrets, not in the browser bundle.
Privacy
The Privacy Policy describes the information GridLane processes, the service providers involved, retention, and your privacy rights. The Terms of Service govern use of the product.
For security or privacy questions, contact support@getgridlane.com.