Internal OneTrust users, matched to the people behind them

Internal users, their login status and last sign-in, so privacy tooling sits in the same review as everything else.

Book a demo

TYPE · SAAS

OneTrust connectorHOURLY SYNCCAPABILITIES

WHAT PLOY DOES

Sync internal usersUsers arrive over SCIM. Only internal users are ingested, so external parties in the tenant are left out of the graph.

READ

Read login statusThe SCIM active flag tells Ploy whether each account can still sign in.

READ

Track access to OneTrustOneTrust is registered as an application and each user has access to it at the application level, with their user type as the entitlement. Groups and roles inside OneTrust are not ingested.

READ

Read last sign-inTaken from the tenant-wide login history feed. The credential needs the user scope for it; without that scope the connector still syncs, just without usage.

READ

2.1WHAT IT UNLOCKS

Three jobs this connector does on day one

SEATS

Who holds a OneTrust login

Internal users are pulled in and matched to employees, with their user type attached. An account nobody owns is visible rather than buried in the tenant.

REVIEWS

Privacy tooling reviews with everything else

OneTrust access appears in the same review as the rest of the estate, with login status and last sign-in on the row, so the owner answers in one pass.

LEAVERS

The leaver run raises the OneTrust account

When someone leaves, their OneTrust account is on the offboarding list with its status and last sign-in. The task stays open until somebody confirms it is closed.

2.3