How it works:
Profiles define the default owner and non-owner access.
Record sharing rules add access when a record matches a condition.
Access can be granted as Hide, View, Modify, or per field.
When multiple rules apply, Mapsly uses the higher access level for each field.
How to set it up:
Map out your hierarchy levels. E.g., Sales Rep → Sales Manager → Regional Manager.
Pick the record field that reflects that hierarchy — Owner, Territory, Team, Region, or a custom field.
Set base permissions on the profile first. This is the floor everyone starts from — sharing rules only add to it, never replace it.
Enable record sharing rules on the entity.
Create a rule that matches records owned by lower-level users, or belonging to a lower-level territory/team.
Set the rule's access level — View or Modify, typically.
Add more rules for other levels or record subsets that need a different access pattern.
Limit to specific fields, if the rule shouldn't expose the whole record.
Test with a user at each hierarchy level to confirm the result matches your design.
Example
Level | Access | How |
Sales Rep | Edit own accounts | Base profile permission |
Sales Manager | View accounts owned by reps | Rule: rep-owned records → View |
Regional Manager | Modify accounts in their region | Rule: region-based records → Modify |
Take an account owned by a rep in the North region: the manager's rule grants View, the regional manager's rule grants Modify. Mapsly combines both rules per field and keeps the highest level — so the regional manager ends up with Modify on that record, even though two separate rules applied to it.
Notes
Sharing rules add access — they never lower what a user already has.
If a user's access is already higher than a rule would grant, that rule simply has no effect for them.
The same record can match multiple rules at once. The resulting access is resolved per field, not per record.