The Three Role Types


role_type: "territory_owner" | "support" | "manager”

Role Types and Roles work together to shape how accounts are grouped, owned, and assigned inside BoogieBoard. BoogieBoard role types fall into one of three categories, each resulting in a different behavior. They are as follows:

Territory Owner

A Territory Owner owns a specific book of business and receives a dedicated territory. This is the primary role used for territory design and account ownership.

A Role whose role type is Territory Owner defines a mutually exclusive partition of accounts within your organization. Each account can belong to exactly one territory owner at any given time, making these roles the foundation of your territory structure.


Screenshot 2025-10-20 at 14.58.09.png

Example

Consider a global sales org that sells both Hardware and Software. You could define two territory owner Role Types: Hardware Owner and Software Owner. When Apple belongs to the West Coast territory, it gets one rep assigned as Apple's Hardware Owner and another (potentially different) rep assigned as Apple's Software Owner. Those assignments stay separate even if both roles point to the same territory.

Account: Apple Inc.
├─ Hardware Owner (Territory Owner Role Type)
│  └─ West Coast Hardware Territory → John Smith
└─ Software Owner (Territory Owner Role Type)
   └─ West Coast Software Territory → Sarah Johnson

Supporting Roles

Supporting Roles are team members assigned to existing territories or business units but who do not receive their own territory. Ideal for BDRs, SEs, CS, or overlay roles that support a specific segment.

Supporting Roles are often pushed back into Salesforce or the CRM as a part of an “Account Team”.

<aside> 🔑

Territory Owner vs Supporting Roles

The key difference between these two role types lies in how accounts are assigned.

In Scenario 1, we want to designate our two BDRs are overlays to our four Account Executives. The outcome looks like this:

// Automated Distribution       // Manual Assignment
AE1 (Territory Owner)           BDR1 (Supporting Role)
├── Account 2                   ├── Assigned to AE1
└── Account 4                   └── Assigned to AE2       
                                
AE2 (Territory Owner)           BDR2 (Supporting Role)
├── Account 6                   ├── Assigned to AE3
└── Account 8                   └── Assigned to AE4

AE3 (Territory Owner)           
├── Account 1
└── Account 3

AE4 (Territory Owner)
├── Account 5
└── Account 7

BoogieBoard will automatically distribute the accounts to create the territories for the Territory Owners. The user will manually assign the BDRs to support specific territories.

Example Scenario 2: BDRs as Territory Owners

In Scenario 2, we want our two BDRs to have a set of accounts that they call on, determined by BoogieBoard. They will get the same bucket of accounts distributed amongst them as the four AEs. The outcome looks like this:

// Automated Distribution       // Automated Distribution
AE1 (Territory Owner)           BDR1 (Territory Owner)
├── Account 2                   ├── Account 2
└── Account 4                   ├── Account 3
                                ├── Account 7
AE2 (Territory Owner)           └── Account 8
├── Account 6
└── Account 8                   BDR2 (Territory Owner)
                                ├── Account 1
AE3 (Territory Owner)           ├── Account 4
├── Account 1                   ├── Account 5
└── Account 3                   └── Account 6

AE4 (Territory Owner)
├── Account 5
└── Account 7

BoogieBoard will automatically distribute accounts in this node twice: once to the AE territory owners and once to the BDR territory owners.

</aside>