Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryAAccount Assignment Rule
AdministrationIntermediate

Account Assignment Rule

An Account Assignment Rule is a rule within Salesforce Enterprise Territory Management that automatically places an Account into one or more sales territories based on field criteria - for example, BillingState, Industry, AnnualRevenue, or a custom flag.

§ 01

Definition

An Account Assignment Rule is a rule within Salesforce Enterprise Territory Management that automatically places an Account into one or more sales territories based on field criteria - for example, BillingState, Industry, AnnualRevenue, or a custom flag. Admins build each rule as a set of filter conditions on the Territory record; when accounts are created or updated (or when a manual 'Run Rules' job executes), Salesforce evaluates the rules and assigns matching Accounts to the territory, which in turn drives territory-based sharing and ownership.

§ 02

In plain English

👋 Study buddy

An Account Assignment Rule tells Salesforce which sales Territory an Account belongs to based on Account field values. You say "if BillingState is TX, put this Account in the Texas territory"; Salesforce runs the rule when Accounts change or on demand and the territory assignment happens automatically. This is how Enterprise Territory Management keeps territory rosters up to date.

§ 03

Worked example

scenario · real-world use

At Meridian Medical Devices, the territory admin configures three Account Assignment Rules on the "West Enterprise" territory: BillingState IN (CA, OR, WA, AZ), Employees > 1000, and a custom flag Target_Segment__c = 'Healthcare'. When a new hospital-system account is imported via Data Loader with those fields set, Salesforce evaluates the rules the next time territory rules run (nightly by default) and assigns the Account to West Enterprise. The regional VP's roster refreshes automatically; no manual territory assignment needed.

§ 04

Why Account Assignment Rule matters

Account Assignment Rules are a component of Salesforce Enterprise Territory Management (ETM), the product that replaced the older Customizable Forecasts/Territory Management 1.0 model. Each rule is defined on a Territory record as a filter expression (AND/OR combinations over Account fields); one Territory can have multiple rules and an Account can be assigned to multiple territories. Admins control evaluation timing: rules run automatically on Account create/edit and can be run on demand via the 'Run Rules' action against the whole territory model.

Assignment drives territory-based sharing - Accounts assigned to a territory grant access to territory members according to the territory's access levels (Read, Read/Write, Owner rights). Mature ETM deployments version and document their rules (often in an external doc or Git-backed manifest) because rule changes can shift Account ownership for thousands of records at once. For teams that need more complex assignment (machine-learned fit, market-specific rules), the Salesforce Maps or partner-built territory-optimization tools layer on top of ETM, but the declarative Account Assignment Rule remains the baseline.

§ 05

How to set up Account Assignment Rule

Account Assignment Rules in older orgs route incoming Accounts to specific owners based on criteria — "new Tech Industry Accounts go to the West Coast SMB team." Salesforce de-emphasized this for direct Account assignment in favor of Lead Assignment + Lead Conversion routing, but the page still exists for legacy use.

  1. Open Setup → Account Assignment Rules

    Setup gear → Quick Find: Account Assignment → Account Assignment Rules. May not appear in newer orgs.

  2. Click New Rule

    If the page is available.

  3. Set Rule Name and tick Active

    Only one Account Assignment Rule can be active at a time.

  4. Save, then click into the rule → Rule Entries → New

    Each Rule Entry routes a subset of Accounts.

  5. For each Rule Entry: set Order, Criteria, and Action

    Order = priority (1 first). Criteria = Field-Operator-Value rows. Action = User or Queue assignment.

  6. Save

    First matching entry wins. Newly-created Accounts matching the rule get auto-routed.

Key options
Order per Rule Entryremember

Priority. First match wins.

Criteriaremember

Field-Operator-Value rows + filter logic.

User or Queueremember

Where the Account goes.

Gotchas
  • Account Assignment Rules require an explicit "Assign using active assignment rule" tick on the New Account form. Without it, manual creates skip the rule.
  • Salesforce has de-emphasized this feature. Modern orgs typically build assignment via Flow on the Account or use Lead Assignment Rules (with Lead-to-Account conversion).
  • Only one Account Assignment Rule can be active at a time. Activating a new one deactivates the previous — plan staging carefully.
§ 06

How organizations use Account Assignment Rule

Meridian Medical Devices

Uses state + employee-count + custom segment fields to auto-assign hospital system accounts to regional enterprise territories, keeping rosters current without manual Territory Administrator action.

Harbor Finance

Runs 'Run Rules' after quarterly M&A updates - imported newly-acquired accounts land into the right advisor territories automatically based on their industry and AUM fields.

Northline Insurance

Maintains their territory rule definitions in a Git-backed manifest alongside the org's DX Project so rule changes are reviewable and auditable.

§

Trust & references

Official documentation

Straight from the source - Salesforce's reference material on Account Assignment Rule.

Keep learning

Hands-on resources to go deeper on Account Assignment Rule.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.
§

Test your knowledge

Q1. Account Assignment Rules are used within which Salesforce feature?

Q2. What triggers an Account Assignment Rule to evaluate an Account?

Q3. Why is it recommended to test rule changes in a planning territory model first?

§

Discussion

Loading…

Loading discussion…