How the operating layer fits together
The main modules are easier to understand as one flow: collect the source data, run the work, then hand clean outputs to finance and leadership.
Employee records
One profile for job data, manager chain, lifecycle status, documents, and activity.
Workflows
Launch onboarding, offboarding, and repeatable tasks with owners and due dates.
Time off
Requests, balances, policies, approvals, and team calendar visibility.
Document control
Request, upload, acknowledge, and protect employee documents in context.
Reporting
Standard reports, saved views, approved-field builder, and scoped CSV exports.
Payroll-ready data
Clean payroll-affecting changes, compensation records, groups, and exports.
Talent programs
Performance cycles, goals, engagement surveys, and compensation reviews.
Admin controls
Member administration, role-based access, audit logs, and integration metadata.
Built around the work each team actually owns
SalsaHR stays useful because each stakeholder sees a practical operating surface, not a generic HR database.
Run the lifecycle
Records, workflows, documents, time off, talent programs, and auditability.
Act faster
Approvals, tasks, goals, and scoped team workflows.
Self-serve
Tasks, requests, documents, goals, reviews, and surveys.
Trust the handoff
Payroll-ready changes, compensation records, dimensions, and exports.
Honest boundaries are part of the product
SalsaHR is useful because it is clear about what it does and does not do.
HR operations, talent workflows, finance-ready reporting, and admin control
The shipped app covers the people operations work shown above, including controlled exports and audit visibility.
No payroll processing, tax filing, AI, or provider sync claims
SalsaHR prepares clean HR data and auditable exports. Payroll execution, EOR/PEO, AI assistants, OAuth, and provider sync remain outside the current public promise.