Employee directory and profiles
Core HR tabs like Job, Compensation and Employment Status are locked — you can't add fields or rename them, so non-US workflows get shoehorned into US-shaped tables.
What people actually say
✕Standard tables on the Job tab (Employment Status, Job Information, Compensation) cannot be modified — fields can't be added or renamed.
Source: FinServ Consulting, BambooHR implementation notes ↗✕BambooHR's modules are designed around US business practices, making the platform a poor fit for global teams with multi-entity reporting needs.
Source: SelectSoftware Reviews, BambooHR ↗✕When critical data is stored in custom tables, core capabilities like onboarding and offboarding email alerts no longer fire — they only read standard tabs.
Source: FinServ Consulting, custom table limitations ↗
We model your employees in Postgres with whatever fields your business actually tracks — UK NI numbers, contractor day rates, multi-entity payroll IDs, custom employment classes — and render the directory with Next.js. There are no protected standard tables: every field is editable, indexed and exportable, and email workflows read from any column you want, not just the ones BambooHR considers canonical.