Early-access documentation

Operate the company ZIP release with evidence, not guesswork.

Install a portal, prepare HubSpot company ZIP data, build exact ZIP5 territories, simulate every decision, and understand the safety boundary before any authorized owner write.

Last reviewed July 15, 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.

01

Getting started

Install with HubSpot, follow the first sync, create a small test program, and run a read-only simulation.

10–20 minutes · Account OwnerOpen guide 02

Prepare HubSpot

Check company country and ZIP values, owner records, permissions, and the exact early-access scope boundary.

Before the first syncOpen guide 03

Build ZIP programs

Assign exact U.S. ZIP5 values manually or merge a local CSV without uploading the source file.

Editor guideOpen guide 04

Simulate, publish, and roll back

Read impact categories, understand the closed write gate, and use guarded publication and rollback safely.

Publisher guideOpen guide 05

Work with exceptions

Understand missing, invalid, unsupported, unassigned, locked, plan-limited, and owner-invalid records.

Operational reviewOpen guide 06

Members and roles

Grant portal-scoped access to synced HubSpot users without creating separate TerritoryLogic passwords.

Account Owner guideOpen guide 07

Uninstall and data deletion

Prepare any desired guarded rollback, disconnect from HubSpot, and understand the purge boundary.

Account Owner guideOpen guide 08

Troubleshooting

Resolve sign-in, sync, ZIP, simulation, write-authorization, and stale-draft problems without unsafe retries.

Error recoveryOpen guide
02 / What is available

Know what a successful early-access test proves.

Available today

  • HubSpot OAuth installation and a bounded company sync.
  • Exact U.S. ZIP5 membership, including ZIP+4 normalization and leading-zero preservation.
  • Whole-ZIP hierarchical territories with fixed owners or nearest-ancestor inheritance.
  • 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.
  • Programs for contacts, deals, tickets, leads, or custom objects.
  • Paid checkout or production transactional email notifications.
03 / Safety principles

Three facts to keep beside every test.

The ZIP decides

Census ZCTA outlines are display approximations. Exact normalized ZIP5 membership—not a polygon, centroid, city, or state—drives the current decision.

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 current company-write OAuth scope, and a fresh publication preview before TerritoryLogic may write.