Flexi HQ
Org structure & blueprint
Every competitor says 'flexible.' Flexi HQ is the control plane that makes it true — the place where Bata configures retail policies, Engro configures manufacturing shifts, and Ufone configures telecom workflows — all on the same product, each on its own configuration.
Your company is not an org chart. It's three legal entities, seven divisions, a matrix reporting line everyone denies exists, and designations that got invented in a CEO-level meeting last year. Flexi HQ captures it the way it actually is — not the way the last HRMS forced you to redraw it.
What Flexi HQ does.
Flexi HQ is the organisational blueprint — legal entities, divisions, cost centres, reporting lines, matrix structures, and designations — that every other Flexi module configures against.
Drag, drop, and configure fields from the Flexi Meta dictionary into onboarding, transfer, exit, and any other form — per tenant.
Configure approval chains, conditional routing, SLAs, and escalations visually. No YAML, no scripts.
Leave rules, attendance rules, payroll components, OT multipliers — all expressible in configuration, not code.
Configurations can be scoped per legal entity, business unit, location, or employee class — so head office and plants can differ.
Every configuration change is versioned. Roll back instantly if something breaks. Test in sandbox before publishing.
Approval workflows for configuration changes themselves — so a rogue admin can't change payroll rules unreviewed.
A Flexi HQ cycle, end to end.
- 1Design
HR admin builds or adjusts forms, workflows, and policies visually in Flexi HQ.
- 2Validate
Changes run against a sandbox with test data before they touch production; dependency analysis flags impact.
- 3Publish
Approved configuration publishes to the tenant — affecting ESS, MobileEdge, and every module from next use.
- 4Monitor
Audit trail captures every change, every publisher, every rollback — available for internal and external audit.
Flexi HQ shares data with these modules.
No data re-entry. No broken integrations. One platform, one data model.