Early-access documentation

Operate ZIP-based ownership with evidence, not guesswork.

Install a portal, choose one or more supported HubSpot objects and map each ZIP property, build one shared ZIP5 territory plan, simulate every decision, and understand the safety boundary before any authorized owner write.

Last reviewed July 29, 2026 · Early-access documentation
01 / Guided workflows

Choose the task in front of you.

Each guide describes the controls available in the current public early-access build. It also names the point where you should stop instead of inventing a workaround.

02 / What is available

Know what a successful early-access test proves.

Available today

  • HubSpot OAuth installation, object-specific authorization, and bounded CRM record snapshots.
  • Exact U.S. ZIP5 membership, including ZIP+4 normalization and leading-zero preservation.
  • Explicit whole-state fallback for ZIP-missing records with usable city and state evidence.
  • Flat whole-ZIP territories with explicit fixed owners and safe exceptions when no valid owner is configured.
  • Local CSV merge and export with no source-file upload and no automatic save.
  • Read-only simulation with categorized, record-level explanations.
  • Guarded publication and rollback machinery for portals whose live-write capability is separately authorized.

Not generally available

  • Live HubSpot owner writes for a newly installed portal.
  • Street-address geocoding, coordinate routing, split-ZIP polygons, or drive-time areas.
  • Round robin, weighted pools, CRM criteria, named-record overrides, or automated rebalancing.
  • Activity programs or association-derived location fields.
  • Paid checkout or production transactional email notifications.
03 / Safety principles

Three facts to keep beside every test.

ZIP first, state second

Census ZCTA outlines are display approximations. Exact normalized ZIP5 membership wins; only a ZIP-missing record can use normalized city/state evidence against explicit whole-state coverage.

Simulation is read-only

Simulating never changes a HubSpot owner. It produces evidence that can later support a separately authorized publication.

Writes fail closed

A portal needs explicit write enablement, the selected object's write scope, and a fresh publication preview before TerritoryLogic may write.