Permission-set-based routing so reps only see leads in their assigned team/territory

Outcome. A rep only sees the leads that belong to their own team or territory, so record visibility matches assignment instead of every rep browsing every territory's pipeline by default.

Workflow map Enrollment, branches and actions at a glance lead-routing-046

flowchart TD
    A[Contact created / Territory set] --> B{Territory value?}
    B -->|north-america| C[Rotate to NA pool - unchanged from lead-routing-001]
    B -->|emea| D[Rotate to EMEA pool]
    B -->|apac| E[Rotate to APAC pool]
    C --> F[Set routed date, notify, create task]
    D --> F
    E --> F
    G[Portal settings: Team-scoped permission sets] --> H[NA reps see only NA-owned records]
    G --> I[EMEA reps see only EMEA-owned records]
    G --> J[Sales ops retains cross-team visibility]

When to use it, when not to

• UseUse it once territory-based routing (lead-routing-001) is already working and the remaining problem is visibility: reps can still see and edit records outside their own territory even though they never get assigned there.
• UseUse it when the org has clean Team structures that map to the same territories the routing workflow already uses, so the two systems reinforce each other instead of drifting apart.
• SkipDo not use it as the routing mechanism itself; permission sets restrict who can see and edit a record, they do not assign an owner. The rotation logic here is unchanged from lead-routing-001, only the settings layer is new.
• SkipDo not use it if the team genuinely needs cross-territory visibility for coverage or collaboration reasons; a visibility restriction that blocks legitimate cross-team handoffs creates more friction than it solves.