Skip to content

Sales — Territory & Quota Definition Registry

After every reorg, CRM and reporting must pick up the new territory and quota map from one effective-dated source.

Why this is needed

  • Territory fights and broken commissions start in Excel maps.
  • Quota definitions must be official for forecasting.
  • RLS can follow territory entities.

Proposed entities in EntiHub

Governance settings

Setting Recommended value Why
approvalRequired true Territory/quota changes need Sales Ops approval.
historyEnabled true History of reorg maps.
allowSameAuthorApproval false Maker/checker separation for sensitive changes.
deletedRetentionDays 90 (or higher) Soft-delete retention for auditability.

Entity definition (YAML sketch)

name: territory
displayName: Territory
domain: Sales
description: Territory
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: territory_code
uniqueConstraints:
  - name: uq_territory_territory_code
    columns: [territory_code]
columns:
  - name: territory_code
    dataType: string
    nullable: false
    maxLength: 32
  - name: name
    dataType: string
    nullable: false
    maxLength: 128
  - name: owner_email
    dataType: string
    nullable: false
    maxLength: 256
  - name: region
    dataType: string
    nullable: false
    maxLength: 32
  - name: effective_from
    dataType: date
    nullable: false
  - name: status
    dataType: string
    nullable: false
    maxLength: 16

YAML sketches

Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.

Sample data

territory_code name owner_email region effective_from status
T-DACH-01 DACH Enterprise a.mueller@co.com DACH 2026-01-01 active

Benefits for the company

  • One map for CRM assignment and reporting.
  • Effective dating for reorgs.
  • Cleaner forecasting inputs.