Platform
One API, shared identity, tenant isolation
Orgix is built on a modular monolith — one database, clear module boundaries, JWT auth, and backend rules as the source of truth for validation, permissions, and business logic.
Single sign-on
Enterprise SSO patterns (including SAML) via auth.orgixapp.com — one identity across People, CRM, and mobile.
Webhooks
Wire Orgix events into your stack for automation, analytics, and downstream workflows.
Module SKU model
Enable HRIS, CRM, Field Force, or Suite per company. Navigation is driven by GET /auth/modules on web and mobile.
Multi-tenant isolation
Each company (tenant) is isolated — data never crosses organization boundaries. Users switch company context with one API call.
Dual authorization
Company roles (SUPER_ADMIN, ADMIN, HR, MANAGER, EMPLOYEE) plus permission groups for fine-grained module access.
Web ↔ mobile parity
Mobile implements the same flows as web — attendance, leave, notifications, and field work — adapted for native UX.
ORGIX ADMIN vs company workspace
Day-to-day HR and operations happen in the company workspace. ORGIX ADMIN (or equivalent platform operator tooling) is a separate experience for system-level operators — companies, global users, billing hubs, audit logs — not the same buyer journey as end-user HR.
Operator console overview →SSO and webhooks are supported; third-party integrations should be confirmed against your contract and release notes.