Sign In + Access Scope
Authenticate, load your tenant context, and confirm role permissions before entering module workspaces.
Documentation Hub
Use this documentation center to onboard teams, run module workflows, integrate via API, and maintain policy-aligned operations.
Recommended sequence for new tenant teams.
Authenticate, load your tenant context, and confirm role permissions before entering module workspaces.
Define clients, LOBs, departments, positions, countries, and sites in Admin > Reference Data.
Start with recruiting, onboarding, employee records, and workforce operations to establish end-to-end flow.
Use dashboard KPIs, queues, and notifications to track SLA risk, approvals, and operational backlog.
Primary module playbooks by business function and role ownership.
Cross-module KPIs and trend monitoring
Requisitions, pipeline, AI-assisted ranking, hiring decisions
Task templates, policy acknowledgements, readiness tracking
Training plans, attendance, coaching acknowledgements
Evaluations, scorecards, quality trend management
Directory, profile actions, approval-gated record changes
Scheduling, swaps, capacity planning, queue operations
Internal chat, customer channels, agent assignment
Project-scoped tickets, SLAs, approvals, escalations
Asset lifecycle, intake batches, reconciliation, licenses
Exit workflow, revocation checks, asset return closure
Scoped content management and client read-only visibility
Core API families and usage patterns for frontend and integration teams.
Base path: /api/v1
Auth: Bearer token + tenant and role claims
Standards: Request/response IDs, tenant scoping, auditability on sensitive actions
| Area | Endpoint Family | Notes |
|---|---|---|
| Authentication | /auth/login, /auth/callback, /auth/session | OIDC flow + role/tenant session context |
| Employee Domain | /api/v1/employees, /api/v1/employee-profile-change-requests | Profile read/write with approval workflows |
| Recruiting | /api/v1/recruiting/* | Requisitions, applications, scoring, decisions |
| Workforce | /api/v1/workforce/* | Schedules, swaps, capacity and queue actions |
| Service Desk | /api/v1/service-desk/* | Tickets, workflows, approvals, SLA operations |
| Inventory | /api/v1/inventory/* | Assets, batches, reconciliation, lifecycle events |
| Notifications | /api/v1/notifications/* | Inbox, preferences, read/dismiss actions |
Operational rules that shape user experience and data handling across modules.
Data access is restricted by tenant and further constrained by client/LOB assignment where applicable.
Navigation, actions, and API outcomes are permission-aware and role-specific.
Sensitive profile and private-data updates remain pending until authorized approval.
Requests, approvals, status transitions, and critical operations are captured for traceability.
Client portal is read-only and restricted to approved client/LOB-scoped content and reporting.
Users manage delivery preferences while policy-governed alerts remain enforceable.
High-frequency workflows that should have documented SOPs for support and UAT.
Suggested content model for growing this into a full docs portal.
Task-driven guides by role with screen context, prerequisites, and expected outcomes.
Data model highlights, queue states, approval transitions, and reporting behavior per module.
Endpoint contracts, payload examples, error formats, auth requirements, and idempotency notes.
Tenant setup, reference data maintenance, permission governance, and client access controls.
Incident handling, SLA escalations, exception workflows, and release readiness checklists.
Versioned updates to behavior, APIs, policies, and role access expectations.