Our organization is set up so that we have 14 different regions, each with a few territories. Each region has a Regional Manager, each territory has Territory Managers, and within each territory we have New Account Managers and Existing Account Managers. In addition, within each region, we have advisory roles (i.e. Marketing, Education, etc.) that work with all the accounts in the region. However, because of the way the accounts role up, we've had to set it up this way:
- Regional Manager
- Territory 1 Manager
- New Account Manager - T1
- Existing Account Manager - T1
- Territory 2 Manager
- New Account Manager - T2
- Existing Account Manager - T2
- Education Support
- Marketing Support
- Territory 1 Manager
This structure (which I've greatly simplified) then has to be replicated for every single region. I am hoping there is a way that I can use properties from the user account record (each user has their region/territory listed) to simply the structure into something like this:
- Regional Manager
- Territory Manager
- New Account Manager
- Existing Account Manager
- Education Support
- Marketing Support
- Territory Manager
Instead of having 14 of these structures, I would then only have one. Accounts would then be shared by both this heirarchy as well as the properties within their user object (region and territory fields).
Is this possible? Is there a better way to go about doing this?
Some final notes:
- Accounts must filter up (regional managers should see all of the territory manager's accounts, but individual territory managers should not see other territory manager's accounts).
- All of the advisory roles should have the 'regional' view, accessing all accounts within their respective region.
- We still need to filter out activties on reports by role somehow (a regional leader would want to see a breakdown of activity within each territory and role, but all of the New Account Managers should not be lumped together as they are in different territories)
Any help or insight would be greatly apprecaited! Thanks in advance.
You really want to use your Role Hierarchy to represent the pipeline and forecasting rollup pattern you need. It is also the key to record access control. Even though you have what seems like a lot to manage, it also provides a very clear picture of how each Rep's contribution fits into the company totals.
