Module guide

Territories

Review territory coverage, representative ownership, map context, and territory-level performance. Creation and simulation live inside the same module family.

2026-07-20Field strategy/territories

Runtime availability

Territory lists and detail pages are customer-visible. Simulation and managed rebalance recommendations can be unavailable in customer-hosted runtime.

Who uses this module

managersadministrators

What users can do

  • Review territory coverage, ownership, and drill into a single territory.
  • Create a new territory or inspect assignment details when your role allows it.
  • Open the simulator to compare scenarios when your runtime supports managed balancing.

Access and approval limits

  • Territory coverage always stays limited to the selected organization.
  • Creation, reassignment, and simulation actions are typically manager or admin lanes.
  • Managed workload rebalance logic is not assumed to run in every runtime.

Key workflows

These workflows describe how the visible customer workspace is intended to be used.

Review a territory

Open the list or detail view to inspect ownership, map context, and current coverage.

  1. 1Filter territories for the active organization.
  2. 2Open a territory card or detail view.
  3. 3Use related links to inspect routes, HCPs, or planning impact.

Use simulation when available

The simulator compares managed workload scenarios without changing live territory ownership until you decide to act elsewhere.

  1. 1Open Territory Simulator from the territory workspace.
  2. 2Review scenario recommendations or the managed-only notice.
  3. 3If no simulation is available, use the current territory metrics and related modules instead.

Core concepts

Territory coverage

Coverage reflects the share of the visible operational scope reached inside a territory.

Reference

Covered screens

`/territories`, `/territories/new`, `/territories/simulate`, `/territories/*`

Troubleshooting

The simulator shows a managed-only message.

  • Confirm whether your workspace is customer-hosted.
  • Continue with the current coverage and assignment views for decision support.

Escalate only if the runtime label does not match your deployment posture.

Connected modules

These areas usually carry the next action, source record, or downstream evidence.

Territories | FieldOrchestrator