- CEO remains at the top as he is suppose to see all the records across
the company.
- Now, for longer run, its always better to create geography-wise
roles. So I would suggest creating 4 roles that report to CEO
(North, East, West & South Directors)
- Now you can create 4 roles for Sales Associate as of now. (North,
East, West & South Sales Associates reporting to their respective
Director)
- Going forward as the hierarchy increases, you can add more roles to
the bottom.
The benefit of this model is - Each director can see data only in his hierarchy. Ex- North Director will not see data of South Sales Associate unless explicitly shared with him.
**CEO**
NorthDirector-------SouthDirector--------EastDirector---------WestDirector
| | | |
NorthAssociate-------SouthAssociate--------EastAssociate---------WestAssociate
Sharing Settings
OrgWideDefaults can be set as per the organization use cases.
While setting OWD on individual objects, always ask -
"Who is the most restricted User in my Org?"
"Can he read and edit all data in the org?" if Yes, public read-write
"Can he atleast read all data in the org?" if Yes, public read-only else private