Topic starter
24/10/2026 8:47 pm
TL;DR: Salesforce access can look compliant at the profile level while still exposing sensitive objects through inherited permissions and sharing rules, according to Oleria Security. Governance needs object-level evidence and continuous review to catch effective access that periodic certifications miss.
Editorial analysis by NHI Mgmt Group, based on content published by Oleria Security: “Identity security & governance for Salesforce”.
Key questions
Q: Why do connected apps and integration users need separate governance from human users?
A: Because they carry their own credentials, scopes, and API rights.
Q: What are the signs that Salesforce access controls are getting out of control?
A: A common warning sign is a mature org where profiles have been cloned and modified repeatedly, leaving old permissions in place and unused profiles behind.
Q: What breaks when Salesforce access is built mainly on profiles?
A: Profiles become overloaded with exceptions, which makes least privilege hard to maintain and even harder to audit.
Practitioner guidance
- Audit effective Salesforce permissions, not just profiles Reconstruct read, edit, and delete rights from profiles, permission sets, permission set groups, role hierarchies, and sharing rules before recertifying access.
- Separate NHI governance from employee access review Track connected apps, integration users, and OAuth credentials as discrete identities with their own owners, scopes, and offboarding events.
- Flag dormant integration users and unused privilege Compare granted Salesforce rights with recent audit activity to identify service accounts and humans whose access exceeds current operational use.
Bottom line: Salesforce access can look compliant at the profile level while still exposing sensitive objects through inherited permissions and sharing rules.
Glossary terms: Effective Access, Permission Drift, Connected App, Object-Level Access
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
25/10/2026 11:12 am
Salesforce identity governance fails at the level of effective access, not identity count: The issue is not how many users or apps exist, but whether controls can reconstruct what each identity can actually reach. Profiles, permission sets, and sharing rules create composite entitlements that are easy to misread in a spreadsheet or license-based review. The practitioner conclusion is straightforward: if you cannot resolve effective access, you cannot certify Salesforce with confidence.
A question worth separating out:
Q: How should teams decide between static reviews and continuous Salesforce monitoring?
A: Use continuous monitoring when rights change through inherited groups, connected apps, or recurring permission set additions. Static reviews are too slow for a system where effective access can change without a formal request, so the control should move from periodic certification to ongoing entitlement correlation.
👉 Read our full editorial: Salesforce access drift exposes hidden NHI governance gaps
This post was modified 6 days ago by NHI Mgmt Group