📌 CTA Knowledge Bytes #7 - Which OOTB Team Sharing Feature to Use

Choosing the wrong sharing mechanism = complexity nightmare + performance issues.

Choosing the wrong sharing mechanism = complexity nightmare + performance issues. Here’s how CTAs match features to use cases:

1️⃣ Territory Management

When to Use:

• Geographic/market-based sales coverage

• Multiple territories per opportunity

• Territory hierarchies with rollup reporting

• Complex assignment rules (account criteria)

• Influence Sharing Rules via implicit sharing 🛡️

Use Cases:

✅ Enterprise sales with regional teams

✅ Multi-product sales with territory overlap

✅ Partner channel management by region

Don’t Use When:

❌ Simple owner-based sharing is sufficient

❌ <100 territories (overhead not worth it)

❌ Territories change frequently (high admin cost)

---

2️⃣ Account Teams

When to Use:

• Multiple roles collaborate on same account

• Need different access levels per team member

• Recurring team structures across accounts

• Influence Sharing Rules via implicit sharing 🛡️

Use Cases:

✅ Strategic accounts with dedicated teams

✅ Account Executive + Sales Engineer + CSM model

✅ Cross-functional account management

Key Feature: Team roles define access level (Read, Read/Write)

---

3️⃣ Opportunity Teams

When to Use:

• Deal-specific collaboration (not account-wide) to open up access

• Multiple stakeholders per opportunity

• Influence Sharing Rules via implicit sharing 🛡️

Use Cases:

✅ Complex B2B sales with specialists

✅ Overlay sellers (inside sales + field sales)

✅ Solution consultants on large deals

Pro Tip: Default Opportunity Teams auto-populate from templates

---

4️⃣ Case Teams

When to Use:

• Support ticket escalation workflows

• Specialist involvement on cases

• Cross-functional case resolution

• Influence Sharing Rules via implicit sharing 🛡️

Use Cases:

✅ L1 → L2 → L3 support escalation

✅ Technical + billing teams on complex issues

✅ VIP customer support with dedicated resources

Key Benefit: Predefined case team roles with access levels

---

5️⃣ Public Groups

When to Use:

• Static user collections for sharing

• Manual or API-managed membership

• Cross-functional teams (not role-based)

Use Cases:

✅ Executive team access to strategic accounts

✅ Project teams needing temporary access

✅ Department-level data visibility

Types: Public Groups, Personal Groups (user-created)

6️⃣ Account Contact Relationships (ACR)

When to Use:

➢ Tracking contact relationships across multiple accounts

➢ Contact visibility without opening record sharing

➢ Reporting on multi-account relationships

⚠️ CRITICAL: ACR does NOT grant record access - only tracks relationships

Use Cases:

✅ Contacts affiliated with multiple companies

✅ Board members serving multiple accounts

---

🚨 Common Mistakes You Must Avoid:

❌ Using Territory Management for <100 territories Why: Administrative overhead > benefit

❌ Account Teams when you need Opportunity Teams Why: Wrong scope (account vs deal), splits don’t work

❌ Public Groups for hundreds of sharing rules Why: Maintenance nightmare, performance impact

❌ Sharing Sets when Sharing Groups make sense Why: Criteria complexity for simple static access

❌ Manual Sharing instead of Teams Why: Not scalable, no structure, reporting gaps

---

💡 CTA Best Practice: “Choose features based on BUSINESS PROCESS, not just technical capability. The right sharing model reflects how teams actually work.”

⚡ Performance Tip: Each sharing mechanism has overhead. Territory Management + Account Teams + Complex Sharing Rules = Recalculation storm. Design holistically!

---

What’s your go-to sharing architecture pattern for complex org structures?

#CTAKnowledgeBytes #SalesforceArchitecture #EnterpriseArchitecture #AI #Agentforce

Salesforce | Salesforce Architecture Talk | Salesforce Partners | Salesforce Architects | Salesforce Admins | Salesforce Developers