Employee data model
Records, custom fields, effective dates, lifecycle events, and change history.
Obsi People · Docs
Guidance for configuring employee data, company structure, integrations, API access, authentication, security, privacy, and administrator ownership.
Records, custom fields, effective dates, lifecycle events, and change history.
Identity, payroll, finance, hiring, collaboration, and document-system setup and field mapping.
Versioned employee-data and event integration surfaces with scoped authorization rather than public unauthenticated access.
API keys, OAuth applications, SSO, and provisioning boundaries where supported by the current platform.
Roles, audit history, retention schedules, legal holds, verified deletion, and privacy-request handling.
Define legal entities, locations, departments, administrators, and launch ownership.
Import employee data, map source fields, validate required values, and resolve duplicate records.
Configure identity and authentication so joiners, movers, and leavers follow the intended access model.
Shared AI capability belongs to Outborn AI rather than recreating the historical product-local Hrive AI surface.
Obsi People