SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Separate three access layers
Zoho CRM roles describe hierarchy and influence record visibility. Profiles define what actions a user may perform. Organization defaults and sharing rules determine which additional records can be viewed or changed. Reviewing only one layer can produce a misleading answer about effective access.
Build the matrix from responsibilities
List representative users and the records and actions their job requires. Include read, create, edit, delete, export, automation administration and webform management where relevant. Add a prohibited action for each role so the test proves both access and restriction.
| Persona | Required | Must not have |
|---|---|---|
| Sales representative | Edit owned deals | Change security configuration |
| Team manager | Review subordinate records | Export unrelated departments by default |
| Webform administrator | Manage approved forms | Delete all CRM records |
The personas are hypothetical and must be replaced with the organisation's actual responsibilities.
Calculate effective access
Check the profile action first, then role hierarchy, default organization permission, peer sharing and custom sharing rules. Zoho notes that higher roles still require the relevant module permission and that sharing rules can extend but not reduce organization-wide access.
- Inventory roles, profiles, groups and defaults.
- Map each test user to one approved responsibility set.
- Use synthetic records owned by different roles.
- Test view, edit, delete and export separately.
- Record unexpected access and its granting layer.
- Retest after hierarchy or sharing changes.
Review with least privilege
Remove access that has no current business need, but do not change a live role based on assumptions. Plan the change, test it with representative accounts and keep a rollback record. Include attachments, notes and email visibility where they inherit access from a record.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.