Permission-based approval routing by territory

Outcome. A discount approval request automatically reaches the correct territory's approver instead of a single fixed person, so the deal-hygiene-015 approval pattern scales past one team without a workflow rebuild per region.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-041

flowchart TD
    A[Deal in pre-Closed-Won stage, discount above threshold, not approved] --> B{Which territory?}
    B -->|North America| C1[Notify Approver North America]
    B -->|EMEA| C2[Notify Approver EMEA]
    B -->|APAC| C3[Notify Approver APAC]
    C1 --> D[Create approval task, matched approver]
    C2 --> D
    C3 --> D
    D --> E[Delay 2 business days]
    E --> F{Still not approved?}
    F -->|yes| G[Escalation to matched approver]
    F -->|no| H[Exit, deal can advance]

When to use it, when not to

• UseUse it once deal-hygiene-015's single-approver discount gate is already working and the team has grown into more than one territory, each needing its own approver.
• UseUse it if a Territory property already exists and is populated reliably, for example from native Territory management (Enterprise) or a custom enumeration maintained by sales ops.
• SkipDo not use it if there is only ever one approver regardless of territory, deal-hygiene-015 already covers that case more simply.
• SkipDo not expect HubSpot permission sets to route the notification automatically by themselves. Permission sets (Enterprise) control who is allowed to edit the Discount Approved property, they do not pick which named person a workflow email goes to, this fiche still needs an explicit territory-to-approver mapping.