A little guidance.
A familiar workspace.
What HLCustomizer changes, how the current pilot works, and what to expect before installing.
Start with an approved installation.
The console currently serves the existing private pilot. Public signup and new early-access requests are closed.
- Sign in to the console using the approved pilot account.
- Select your organization and register the installation.
- Wait for workspace ownership approval. A pending registration does not supply a working snippet.
- Once approved, copy the installation’s snippet and follow its installation instructions.
Domain verification and installation approval are separate. Adding or verifying a domain does not change the SDK’s current supported scope.
Keep preferences easy to revisit.
Navigation and Appearance settings are saved for the workspace in this browser profile, rather than following a signed-in user across devices. Temporary interaction state is not saved as a preference.
Your startup display choice controls the initial view. It is separate from the current display and temporary hover or Focus recovery.
- Adjust spacing and recent-page appearance.
- Open feature guides without changing preferences.
- Use Restore defaults and Undo to revisit changes.
A selected release applies on refresh.
The console’s delivery status describes the release selected for the next HighLevel refresh. It does not certify which release an already open tab is running.
Keep the approved installation snippet unless instructed to replace it. Changing a registration or requesting a branded hostname does not automatically edit HighLevel’s saved custom code.
Know the current boundary.
The SDK is currently limited to the existing private pilot. Broader workspace onboarding and managed domain activation remain in development.
Desktop enhancement requires a page viewport wider than 1024 CSS pixels and supported native layout hooks. Below that boundary, or when the host layout is unsupported, HLCustomizer yields to HighLevel’s native navigation.
Hover interactions require a suitable pointer. Keyboard and touch users retain explicit controls. HighLevel continues to own routing, native menus, permissions and workspace switching.
Private-pilot testing is not a claim of compatibility with every HighLevel layout, browser or future update.