Changing permissions is not just adding or removing access. Review object permissions, FLS, sensitive fields, user assignments, and permission set overlap before changing Salesforce permissions.
Read-only diagnostics · Review-ready workbooks · No package install · No Connected App
A Salesforce permission change impact review is the process of understanding who has access to what before making changes to profiles, permission sets, or field-level security — and what the change will affect when it goes in.
Permission changes are often treated as straightforward — add a permission, remove a permission. In practice, permission changes in complex orgs affect users in ways that are not obvious until the review uncovers the overlap, the sensitive field exposure, or the external user access that was not part of the intended scope.
Three common permission change surprises that review evidence can help prevent:
The review does not prevent changes. It creates evidence that supports the right change.
Relevant Workbook
Permission & FLS Audit maps profiles, permission sets, object permissions, FLS, user assignments, and access-risk signals into a review-ready XLSX workbook before permission changes are applied.
Review object-level permissions on the affected profiles and permission sets, field-level security on fields in scope, sensitive field exposure for the users who will be affected, permission set overlap that may create unintended cumulative access, external user access if applicable, and user assignment counts to understand the scope of the change.
Salesforce grants the most permissive access when multiple permission grants apply to the same user. If a user has a profile that denies FLS on a field but also has a permission set that grants FLS on the same field, the permission set grant takes precedence. Reviewing FLS across both profiles and permission sets is necessary to understand actual access.
Permission set overlap means a user has multiple permission sets that grant access to the same objects or fields. When changes are made to one permission set, the expected impact on a user's access may be masked if another permission set also grants the same access. Review active user assignments across all relevant permission sets before changing access.
Yes. External users, community users, and guest users often have different access patterns than internal users. Sensitive field exposure, object access, and FLS for external users warrant a separate review — because the consequence of over-exposure may be higher and the user type may not appear in standard internal permission reviews.
Permission & FLS Audit maps profiles, permission sets, object permissions, FLS, user assignments, and access-risk signals for selected objects in a review-ready XLSX workbook. It supports the review conversation before permission changes are made — not after.
Run a read-only KeelCadence diagnostic to surface metadata, access, automation, field, and readiness signals before cleanup, UAT, imports, handoff, or change work.
Read-only · No package install · No Connected App setup · No Salesforce writes
Trust & Security
KeelCadence uses session cookies and Google Analytics 4 for site usage insights. GA4 does not receive Salesforce credentials, Org IDs, Report IDs, or payment data. You can opt out for this browser.