OGRHCanonical contracts
Vendor data is mapped to stable OGRH business objects.
HRIS integration
Keep your systems of record. Unify the experience.
OGRH connects tools according to the APIs and capabilities they actually expose, without pretending every vendor supports the same operations.
A capability-led integration model
Each source declares what it can read or write. OGRH checks these capabilities before presenting an action to the user.
Controlled writes
Outbox, retries and idempotency protect sensitive operations.
Mixed landscape
TeamsRH, Lucca, Silae, Chronotime, Kelio and other tools can coexist by target capability.
From request to auditable action
1Express the need
2Review structured information
3Authorize and approve
4Execute and track
Frequently asked questions
Do all connectors offer the same scope?
No. Available actions depend on each vendor API and the customer configuration.
Can a native module replace a missing API?
Yes. A capability can be native, external or disabled.
What can the OGRH MCP server access?
Its OAuth discovery publishes ogrh:self:read, ogrh:team:read, ogrh:company:read, ogrh:cabinet:read and ogrh:firm:read. Each tool also checks OGRH permissions and the user’s data scope. The server is read-only and cannot approve or change HR operations.