Vendor territory dashboard

This authenticated portal now centers Phase 4: territory setup cues, territory-scoped inventory browsing, backend-authored redaction labels, and Mike/global reuse messaging. It stays below paid reveal, included credits, and export workflows.

Access unavailable for your role.

Authenticated portal

Signed out

The admin shell stays behind Cognito while backend policy decides whether a vendor or Mike session can see territory data.

Phase 4 boundary

Below reveal

The dashboard points to territory setup and redacted inventory, but it does not open paid reveal, credits, or exports.

Admin API

Waiting

Separate admin API surface is scaffolded with admin-domain CORS before territory-scoped inventory is requested.

Territory seed data

Pending

Phase 4 territory fixtures stay conservative until the inventory browser loads real rows.

Role policy gate

Signed out

This data is restricted by role, vendor, territory, entitlement, or suppression policy.

Audit primitive

Pending

Append-only history remains the rule before territory edits, contact-state changes, and Mike overrides are exposed.

Phase 4 workbench

Territory browser

Open the vendor map/list/detail surface with territory-scoped inventory, backend-authored redaction labels, and Mike reuse cues.

Inventory queue

Review territory-filtered records with contact-state affordances, click-to-call gating, and suppression labels.

Vendor territory

Configure ZIP and radius territory cues, see tier limits, and keep broader-access decisions backend-authored.

Operating metrics

Summarize storms, candidates, leads, vendors, tiers, and source breakdowns without surfacing exports.

Territory setup cues

ZIP list and radius

Vendors configure territory by ZIP list and radius, but tier rules and broader access continue to come from the backend.

Mike/global reuse

Emmaus Guidance administrators use the same discovery surface globally, while the backend distinguishes admin override from vendor access.