Sales CRM · Feature guide

Use pipeline and territory scopes in forecasts

Create forecasts for a defined sales segment without changing record access or silently following territory-tree edits.

Audience: authorised staffPermission: Administrator to create periods; Sales CRM viewing access to inspect themReviewed 30 October 2026

Where to goSales CRM → Forecast & targets → Submissions & review → Open period → Pipeline scope / Territory scope

Before you start

Use your own authorised staff account in the intended Pixie CRM workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.

Follow these steps

Select a pipeline to limit the evidence to its opportunities, or retain All pipelines.
Select a territory to include opportunities with that saved territory classification.
Choose Selected territory only, or Include its current active descendants.
Create the period and verify its scope in the header.
Use a separate period for another currency or a materially different scope.

Behavior and limits

The territory IDs included at creation are fixed. Later parent/child changes or new descendants do not automatically change the period definition.
The opportunity’s current saved territory assignment is still used when measuring live evidence or a new submission. Moving an opportunity into or out of the fixed set can therefore change future evidence.
The period does not rerun territory matching rules, reassign opportunities or grant any new access.
All territories includes unclassified opportunities. A selected territory scope excludes opportunities without a matching saved classification.
Scope is a filter, not a manager hierarchy. Review permission still requires View all deals plus the forecast review capability; territory membership alone does not grant review access.
A selected pipeline and territory apply together. Empty intersections can correctly produce zero evidence.

Check it worked

Check one included and one excluded opportunity against the selected pipeline, currency and assigned territory.
Confirm the displayed territory count matches the intended fixed set when the period is created.

Troubleshooting

If a new child territory should belong to a later forecast, create a new period with the updated scope.
If a record should be classified differently, use the ordinary territory-routing workflow with its existing permissions; forecast creation does not classify it.
If you need a different scope for an existing period, close it with a reason and open a correctly scoped period.