Skip to content
Salesforce coverage Federated identity governance

Salesforce access governance

SafePaaS governs segregation of duties, privileged access and configuration change inside Salesforce — reading User, Profile, Permission Set, Object and Field Permissions and Sharing model, and testing policy against them.

Inside Salesforce, not beside it — the same rule book that governs every other system you run.

Book a Demo See How It Connects
Profile read as Salesforce defines it, down to the sharing model Every snapshot re-tested in full, so a conflict reintroduced since the last one surfaces Across your estate Salesforce and every other system assessed together, so a duty held here and a duty held elsewhere meet One rule book applied across every system in the process, not one tool per application
Coverage at a glance

What SafePaaS reads, controls and monitors in Salesforce

Area Reads Controls Monitors
Access and segregation of duties User, Profile, Permission Set, Object and Field Permissions and Sharing model, and who holds each one SoD rules at the level of the entitlement itself; request-time prevention; simulation of a role change before it is applied; emergency access with a reason and an expiry New conflicts introduced by an entitlement change, expired assignments, and standing privilege nobody reviews
Audit, risk and compliance Control test results, exceptions, approvals and the versioned Salesforce rule set One Salesforce control mapped to SOX, ITGC and internal policy; exceptions with an owner and an expiry Test status against each Salesforce control, and exceptions approaching expiry
Identity 360 — NHI and AI agents Human users, service and integration accounts, and the AI agents acting on a user’s behalf The same SoD policy applied to non-human identities and AI agents as to people Standing authorization held by unattended integrations, and what each non-human identity can actually do
The entitlement model we read

A Salesforce user’s authority is five layers below the role name

SafePaaS reads the Salesforce security model as Salesforce defines it: user, profile, permission set, object and field permissions, sharing model. Each layer is resolved, not assumed.

Only the deepest layers say what a user can actually do, and where. Everything above them is a container.

Figure 1 How SafePaaS resolves a Salesforce user to effective authority
  1. Layer 1 User
  2. Layer 2 Profile
  3. Layer 3 Permission Set and its assignment
  4. Layer 4 Object and Field Permissions object-level and field-level access
  5. Layer 5 Sharing model record-level access, separate from the two above

A container in this chain can be widened while keeping the name an access review sees, and the deepest layer differs with every assignment. That is why SafePaaS tests the authority a user actually resolves to, not the label attached to it.

Coverage in detail

How each area works in Salesforce

How does SafePaaS enforce segregation of duties in Salesforce?

SafePaaS Enterprise Access Monitor tests SoD rules against an ERP Snapshot of your Salesforce security model — user, profile, permission set, object and field permissions, sharing model — rather than against the live system, so a test is repeatable and a result is defensible.

Modules Enterprise Access Monitor Enterprise iAccess Enterprise Roles Manager
▸ Defines rules at the level of the entitlements themselves, not just the user list, so a conflict is found where it actually lives ▸ False-positive filters remove inactive users, expired assignments and end-dated roles before anyone reviews a result ▸ Detects conflicts that span Salesforce and the rest of your estate, so a duty held in one system and a duty held in another are assessed together rather than separately ▸ Enterprise Roles Manager simulates a role change before it is applied, so a change does not reintroduce the violation you just remediated ▸ Violations carry status — Open, Closed, Remediation, Exception — with workflow, reminders and ITSM ticketing ▸ Mitigation records the compensating control and its evidence where a conflict cannot be removed ▸ Emergency access is granted with a stated reason, a time box, and a log of everything done while elevated
Connection

How does SafePaaS connect to Salesforce?

SafePaaS extracts through the platform’s own service interfaces — SOAP per security object, REST for transactions, or a direct database connection where the platform is not cloud-hosted.

Inside Salesforce → SafePaaS extraction SOAP services per security object returning XML; REST endpoints returning JSON for occurrences; a direct database connection where the platform runs on-premise.
Transfer → DataProbe The collected data is pushed out to SafePaaS through DataProbe.
Normalize → DataPaaS The transformation layer. Normalizes the data where required so one rule book can test it.
Result ERP Snapshot The point-in-time copy every module tests against — SoD, monitoring, certification and audit evidence alike.
What is read User, Profile, Permission Set, Object and Field Permissions and Sharing model How data moves Everything collected lands in the FSOD_* open interface tables, and DataPaaS normalizes it from there First snapshot A baseline of every user, role and entitlement assignment, and the first SoD test result set against your own rule book Protection Traffic terminates behind a WAF and an API gateway; the snapshot is tenant-isolated at rest
What runs inside Salesforce Nothing Extraction runs through the platform’s own service interfaces, so no SafePaaS component is deployed into it.

Because every governance module tests the snapshot rather than the live system, the same rule book applies to Salesforce and to every other system in the same business process.

Coexistence

Does SafePaaS replace SailPoint, Entra ID or my existing IGA?

No — and that is the point of federated identity governance. What your identity platform cannot see is what a role permits once the user is inside Salesforce, because that answer lives five layers down in the security model Salesforce publishes.

Your identity platform owns

The account

Joiners, movers and leavers Birthright access The request workflow Provisioning a user into Salesforce, and recording that they hold a role
SafePaaS owns

What the role permits

The entitlement behind the role name SoD across Salesforce and the rest of the estate Configuration and transaction change inside Salesforce Findings handed back to your IGA

So a certification in your IGA reflects the entitlement rather than the role name, and an access request is checked for SoD before it is approved.

FAQs

What Salesforce teams ask first.

The security model as Salesforce defines it: user, profile, permission set, object and field permissions, sharing model. SafePaaS resolves the chain rather than recording the role name, because the role name is a container and the permission lives below it.

Nothing inside the application. Extraction runs through its own service interfaces. Everything collected is pushed out to DataProbe, where DataPaaS normalizes it into the snapshot every governance module tests.

Every test runs against a snapshot taken at a point in time, and Enterprise Roles Manager simulates a role change before it is applied. A change that would reintroduce a remediated conflict is visible before it reaches production rather than at the next review.

Yes. Identity 360 inventories service and integration accounts alongside human users and shows what each can actually do, which is where standing privilege usually sits.

A baseline of every user, role and entitlement assignment, and the first SoD test result set against your own rule book — typically the first time the estate has been assessed against one rule book rather than several.

No. Your identity platform keeps the account, the joiner-mover-leaver process and the request workflow. SafePaaS governs what the entitlement behind the role actually permits, and hands findings back, so a certification reflects the entitlement rather than the role name.

Go deeper on business application governance
Pillar Identity governance without enterprise complexity Pillar Policy-based access governance across the estate Index All application coverage
Next step

See how SafePaaS governs a Salesforce estate

A working walkthrough against a demo environment, with a specialist who can map what you see onto the roles, organisation structure and audit pressure you actually have.

What the walkthrough covers How the entitlement chain is read as Salesforce defines it — user, profile, permission set, object and field permissions, sharing model An SoD conflict traced from the rule to the entitlements that create it How a role change is simulated before it reintroduces a remediated conflict Where SafePaaS sits relative to the IGA and GRC tooling you already run