HR & people data
Lifecycle signals, from your HRIS.
Owlie reads HR-sourced lifecycle state for joiners, movers, and leavers, and turns it into access changes through the standard governance pipeline. BambooHR and Workday are the named HRIS connectors at launch, both sync-only sources of truth. Everything else runs through the in-app builder.
The signal
What Owlie reads from HR.
Employee records, lifecycle state (active, on-leave, terminated), manager relationships, department and title attributes. When multiple sources publish the same attribute, identity attribute governance decides precedence, so “email preferred from Workday, falls back to Google Workspace” is a configured policy.
Attribute precedence depth — Governance model.
Live at launch
Named coverage.
BambooHR
Sync-only employee records supply identity attributes and manager relationships. Mapping status and termination dates to lifecycle state takes an admin-configured attribute mapping.
Workday
Workers, organizations, supervisory orgs, and jobs, with sync-only access like BambooHR. Derives active-vs-terminated lifecycle from the worker’s termination date by default, feeding JML signals and org structure.
For everything else
Beyond BambooHR and Workday.
Rippling, Gusto, and custom HR tables run through the in-app connector builder. Most HR systems expose an OAuth 2.0 or API-key REST surface the builder shapes directly; the differences are field names and pagination. Request native support for another HRIS and we’ll discuss its priority.
Keep reading.
JML scenario
The lifecycle story end to end — HR signal to provisioned access.
Governance model
Per-attribute source-of-truth rules, precedence, and fallback.
Custom connectors
The in-app builder for systems we don’t ship native coverage for.
Request an integration
Tell us which HRIS. We’ll say yes, no, or builder.