Here's my situation:
An Account record has a custom lookup field "CSM" that is the client manager. When the Account becomes a "client", the Account is automatically added to a CSM's Territory via rules. The CSM can then access the Account, Contacts, and all related records. This works great.
We now have a "CSA" (associate) who is also assigned to Accounts - across territories - to help the CSM. The CSA's will need access to the Account AND related records like Contacts to function.
Here's what I've tried:
1) Automatically assign the CSM and automatically assign the CSA Territories, each based on their different rules. The Accounts get placed in both territories, but the related records like Contacts are not automatically assigned to either territory. (this is documented behavior I learned)
2) Automatically assign the CSM territory based on a rule, and manually assign the CSA. It works for the Account, but not any of the related records - they get no territory assigned.
3) Tried to set the CSA lookup field to "Allow Record Accessibility". I thought this was going to be perfect. I set the CSA field to the right person, and they can then indeed see the Account, but NOT the related records.
I was hoping #3 was my answer so I could better manage what Accounts a CSA could see, but without related records like Contacts, it's useless.
What's a good way to construct a manageable access model here?