TECH **Salesforce Role Hierarchy & Territory Management: Zero-Fluff Study Guide**

Salesforce Role Hierarchy & Territory Management: Zero-Fluff Study Guide

For Admins Who Need to Ship, Not Just Pass Exams

1. What This Is & Why It Matters

You’re the Salesforce Admin for a 500-person sales org. The VP of Sales just emailed you:

"We’re restructuring teams. West Coast reps now report to a new regional manager, and we need visibility rules updated by EOD. Also, the enterprise team in Europe can’t see North America’s deals—fix it."

If you don’t master Role Hierarchy and Territory Management, you’ll either: - Break visibility: Reps see deals they shouldn’t (compliance violation).
- Break reporting: Dashboards show wrong numbers (VP yells at you).
- Break automation: Approval processes route to the wrong manager (deals stall).

Role Hierarchy = Who reports to whom (org chart). Controls record access (e.g., managers see their team’s records).
Territory Management = Who sells where (geography, product line, customer size). Controls record assignment (e.g., "All deals in Germany go to Team Berlin").

Superpower: You can restructure a 10,000-record org in 30 minutes without touching individual records.

2. Core Concepts & Components

Role Hierarchy

• Role: A job title (e.g., "Sales Rep," "Regional Manager") that defines data visibility.
• Production insight: If you skip roles, users see only their own records (default private sharing model).
• Role Hierarchy: A tree where higher roles see all records owned by roles below them.
• Production insight: A CEO role at the top sees everything. A manager sees their team’s records + their own.
• Sharing Settings: Rules that override hierarchy (e.g., "Grant Read/Write to all users in the same role").
• Production insight: If you enable "Grant Access Using Hierarchies," managers always see their team’s records, even if sharing rules say otherwise.
• Implicit Sharing: Automatic access for account owners to related records (e.g., if you own an Account, you see its Opportunities).
• Production insight: This is not controlled by roles—it’s hardcoded. Disable it via Sharing Settings if needed.

Territory Management

• Territory: A group of accounts/opportunities based on rules (e.g., "All accounts in Germany with >$1M revenue").
• Production insight: Territories do not replace roles—they complement them. A user can be in multiple territories.
• Territory Hierarchy: A tree where parent territories inherit child territories’ records (e.g., "Europe" includes "Germany" and "France").
• Production insight: If you move a territory under a new parent, all its records reassign automatically.
• Territory Assignment Rules: Criteria that auto-assign records to territories (e.g., "Billing Country = Germany").
• Production insight: Rules run nightly by default. For real-time assignment, use Process Builder or Flow.
• Territory Access Levels: Defines what users in a territory can do (e.g., "Read Only," "Read/Write").
• Production insight: If a user is in two territories with different access levels, they get the most permissive level.
• Territory Model: A container for territories (e.g., "FY2024 Model"). You can have multiple models (e.g., test vs. production).
• Production insight: Activating a new model reassigns all records—do this in a sandbox first!

3. Step-by-Step Hands-On: Restructure a Sales Team in 30 Minutes

Prerequisites

• System Admin permissions in a Sandbox (never test in production!).
• A CSV of users with their new roles/territories (example below).
• Backup: Export all Account/Opp records via Data Loader (just in case).

Task: Reorg a Sales Team from Flat to Regional

Scenario: Your org has 50 reps reporting directly to the VP. You need to: 1. Create 3 regional manager roles (West, Central, East).
2. Assign reps to their managers.
3. Ensure managers see their team’s records.
4. Assign accounts to territories based on Billing State.

Step 1: Build the Role Hierarchy

1. Go to Setup → Roles → Set Up Roles.
2. Delete the existing hierarchy (if flat):
3. Click Delete Role on the top role (e.g., "CEO").
4. Confirm (this does not delete users, just the role).
5. Create the new hierarchy:
6. Click Add Role.
7. Role Name: "VP of Sales" (top of hierarchy).
8. Role Label: "VP Sales".
9. This role reports to: "--None--" (top of the tree).
10. Click Save.
11. Add regional managers:
12. Under "VP of Sales," click Add Role.
13. Role Name: "West Regional Manager".
14. Role Label: "West RM".
15. This role reports to: "VP of Sales".
16. Repeat for "Central RM" and "East RM".
17. Assign users to roles:
18. Go to Setup → Users → Users.
19. Click Edit on a user (e.g., "John Doe").
20. Under Role, select "West Regional Manager".
21. Click Save.
22. Bulk assign: Use Data Loader to update the UserRoleId field (get IDs from Setup → Roles).

Verification: - Log in as a West RM.
- Go to Accounts → All Accounts.
- You should see only accounts owned by West reps (if sharing is private).

Step 2: Set Up Territory Management

1. Enable Territory Management:
2. Go to Setup → Territory Settings.
3. Click Enable Enterprise Territory Management.
4. Click Save (this may take a few minutes).
5. Create a Territory Model:
6. Go to Setup → Territory Models.
7. Click New Territory Model.
8. Name: "FY2024 Reorg".
9. Click Save.
10. Create Territories:
11. In the "FY2024 Reorg" model, click New Territory.
12. Name: "West".
13. Parent Territory: "--None--" (top-level).
14. Click Save.
15. Repeat for "Central" and "East".
16. Add Territory Assignment Rules:
17. In the "West" territory, click Assignment Rules → New Rule.
18. Rule Name: "West Accounts".
19. Criteria:
    • BillingState equals CA, OR, WA, NV, AZ.
20. Click Save.
21. Repeat for other territories (e.g., "Central" = TX, CO, UT, NM).
22. Assign Users to Territories:
23. In the "West" territory, click Users → Add Users.
24. Select the West RM and West reps.
25. Set Access Level to "Read/Write".
26. Click Save.
27. Activate the Territory Model:
28. Go to Setup → Territory Models.
29. Click Activate next to "FY2024 Reorg".
30. ⚠️ Warning: This reassigns all records based on rules. Confirm in sandbox first!

Verification: - Go to an Account in California.
- Check the Territory field (should say "West").
- Log in as a West rep → they should see the account.

Step 3: Automate Territory Assignment (Real-Time)

Problem: Territory rules run nightly. For real-time assignment: 1. Create a Flow:
- Go to Setup → Flows → New Flow.
- Select Record-Triggered Flow.
- Object: Account.
- Trigger: "A record is created or updated".
- Condition: BillingState is changed.
2. Add an Action:
- Click + → Action.
- Search for "Assign Territory to Record".
- Record ID: {!$Record.Id}.
- Click Save.
3. Activate the Flow.

Verification: - Update an Account’s BillingState to "CA".
- Refresh the page → Territory should update immediately.

4. ? Production-Ready Best Practices

Security

• Least Privilege: Don’t put all users in the "CEO" role. Start with private sharing and open up as needed.
• Territory Access: Set default access to "Read Only" unless reps need to edit.
• Audit Trail: Enable Setup → Security → View Setup Audit Trail to track role/territory changes.

Cost Optimization

• Avoid Overlapping Territories: If a record matches multiple territories, it’s assigned to all of them (duplicates = confusion).
• Use Public Groups for Exceptions: Instead of creating a new territory for 2 users, use a Public Group + Sharing Rule.

Reliability & Maintainability

• Naming Conventions:
• Roles: [Department] [Level] (e.g., "Sales Rep", "Sales Manager").
• Territories: [Region] - [Segment] (e.g., "West - Enterprise").
• Sandbox Testing: Always test role/territory changes in a Full Sandbox first.
• Backup Before Activating: Export all records via Data Loader before activating a new territory model.

Observability

• Monitor Assignment Errors:
• Go to Setup → Territory Settings → Assignment Errors.
• Fix records that failed to assign (e.g., missing BillingState).
• Dashboards:
• Create a Territory Coverage dashboard to spot unassigned accounts.
• Use Role Hierarchy in reports to show manager-level rollups.

5. ⚠️ Common Mistakes & Traps

6. ? Exam/Certification Focus

Typical Question Patterns

1. "Which feature controls record visibility for managers?"
2. ✅ Role Hierarchy (not Sharing Rules or Profiles).

3. ⚠️ Trap: "Sharing Rules" can override hierarchy, but hierarchy is the default.

4. "A user is in two territories with different access levels. What do they get?"

5. ✅ Most permissive access (e.g., Read/Write > Read Only).

6. "How do you assign records to territories in real-time?"

7. ✅ Flow or Process Builder (not nightly assignment rules).

8. "What happens when you activate a new territory model?"

9. ✅ All records are reassigned based on the new rules.

Key ⚠️ Trap Distinctions

7. ? Hands-On Challenge (With Solution)

Challenge

"You have 100 accounts in Texas. Create a territory for 'Central' and assign all Texas accounts to it. Then, give a user named 'Alice' Read/Write access to the territory. Verify she can see the accounts."

Solution

1. Create the Territory:
2. Go to Setup → Territory Models → [Your Model] → New Territory.
3. Name: "Central".
4. Parent Territory: "--None--".
5. Click Save.
6. Add Assignment Rule:
7. In "Central," click Assignment Rules → New Rule.
8. Rule Name: "Texas Accounts".
9. Criteria: BillingState = TX.
10. Click Save.
11. Assign User:
12. In "Central," click Users → Add Users.
13. Select "Alice".
14. Set Access Level to "Read/Write".
15. Click Save.
16. Activate the Model (if not already active).
17. Verification:
18. Log in as "Alice".
19. Go to Accounts → All Accounts.
20. Filter by Territory = Central → you should see the Texas accounts.

Why It Works: - Territory rules auto-assign records based on criteria.
- Users in the territory inherit access to its records.

8. ? Rapid-Reference Crib Sheet

Role Hierarchy

• Default Sharing Model: Private (users see only their own records).
• Grant Access Using Hierarchies: ✅ Enable in Sharing Settings for managers to see team records.
• Implicit Sharing: Hardcoded access (e.g., Account owner sees Opportunities). Disable in Sharing Settings.
• Bulk Assign Roles: Use Data Loader to update UserRoleId.

Territory Management

• Enable: Setup → Territory Settings → Enable Enterprise Territory Management.
• Assignment Rules: Run nightly unless automated via Flow.
• Access Levels: Read Only, Read/Write, or No Access.
• Activate Model: ⚠️ Reassigns all records—test in sandbox first!
• Real-Time Assignment: Use Flow with "Assign Territory to Record" action.

CLI/Data Loader Snippets

# Export all Accounts with Territory info (for backup)
sfdx force:data:soql:query -q "SELECT Id, Name, Territory2Id FROM Account" -u YourOrgAlias -f csv > accounts_backup.csv

# Bulk update User Roles (get Role IDs from Setup → Roles)
sfdx force:data:bulk:upsert -s User -f users_with_roles.csv -i Id -u YourOrgAlias

9. ? Where to Go Next

1. Salesforce Help: Role Hierarchy
2. Salesforce Help: Territory Management
3. Trailhead: Role Hierarchy & Sharing
4. Trailhead: Territory Management

Final Pro Tip:

"Role Hierarchy is for people, Territory Management is for places. If you’re assigning records based on geography, use territories. If you’re controlling visibility based on org chart, use roles. Mixing them up is like using a hammer to screw in a bolt—it might work, but it’ll be messy."