HR & people data
Lifecycle signals, from your HRIS.
Owlie reads HR-sourced lifecycle state — joiners, movers, leavers — and turns it into access changes through the standard governance pipeline. BambooHR is the named connector at launch. Everything else is a builder workflow.
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 policy, not a one-off script.
Attribute precedence depth — Governance model .
Live at launch
Named coverage.
BambooHR
Employee records, sync-only at launch. Good for HRIS-driven JML signals and attribute enrichment.
For everything else
Beyond BambooHR.
Workday, Rippling, ADP, Gusto, and custom HR tables — the in-app connector builder handles these. 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 HRIS coverage if you need it on the roadmap.
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.