Hi Wind,
this is a pretty complex question, but I will try to break the parts down one by one to simplify the matter:
organizational structure = Structural base of the whole system and central source of organizational information.
territory management = Specific for sales teams who want to segment the market within specifics specifications to optimise sales work (based on area, customer group, sales potential, etc.).
Account team = Individuals who are responsible for a single account.
All of these factors are intertwined, but can also be seperate from each other. It depends on the system configuration that you enable. Fact is: You can create a system without a territory management or even without an account team (which does not really make sense), but no system survives without an organizational structure.
For example speaking about access user management: If you create a specific role for sales reps, the sales rep should only see and edit the customers that he is responsible for. So when he is a part of the account team, he can do so. The same goes for restriction on the basis of the territory or the organizational structure, so again, it depends on the actual use case. You can apply those specific settings within the restriction rules.
The same also goes for reports or the documents management, although the administrative part as in restricting the access are made in a different spots in the system.
I hope my answer helped you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.