SaleSprint LogoSaleSprint
Workforce & HR

HR Shouldn't Be a Separate Island

The POS already knows who was on shift and what they sold. SaleSprint puts employees, leave, attendance, permissions and approvals on that same platform — nine HR entities, one record of who did what.

Manager and staff reviewing the week's roster together around a laptop

Nine HR Entities

Employees, departments, positions, contracts, leave, attendance, shifts, staff documents and role assignment — the full record, not a name list.

Leave, Attendance and Shifts

Who is rostered, who turned up, who is on leave — kept at the same branch and date scope the rest of the platform uses.

Location-Scoped Permissions

Reduce a manager's access at one specific branch without rebuilding their role. Negation is per-location, so one exception stays one exception.

Approval Routing

Requests route to the right person, with thresholds deciding what needs a signature and reminders chasing what has been sitting too long.

Audit Trail

Who did what, when and from where — captured across the platform. Failed access attempts are logged too, not silently dropped.

Commission and Tips

Handled in the verticals that need it — salon stylists and restaurant servers earn against the sales they actually made.

What is in the workforce module

Nine entities, each a proper screen with its own list, filters and history — and all of them joined to the person standing at the till.

Employees

The person record everything else hangs off — identity, role, branch, status.

Departments

Group staff the way the business is actually organised, across branches.

Positions & job titles

What the job is, separate from who is currently doing it.

Contracts

Terms, dates and type of engagement, kept with the employee record.

Leave

Requests, entitlement and balances, routed for approval like any other document.

Attendance

Who turned up, when, and at which location.

Shifts

Who is rostered, so the till and the roster agree with each other.

Staff documents

Contracts, IDs and certificates filed against the employee, not in a drawer.

Roles & assignment

What each person may do, per branch, enforced everywhere in the product.

Access control that survives a real org chart

Real businesses are full of exceptions. One manager covers three branches but should not touch pricing at the newest one. Most systems make you invent a fourth role for that. SaleSprint lets you take the permission away at that location and leave everything else alone.

  • Role first

    Start from a role that describes the job, not the person.

  • Negate per location

    Remove a specific permission at a specific branch. No role sprawl.

  • Enforced everywhere

    Menus, buttons and reports all respect the same permission set.

  • Logged either way

    Granted actions and refused attempts both land in the audit trail.

Kwame — Branch Manager
3 locations
Osu branchFull manager access
Spintex branchFull manager access
Tema branchPrice override removed

One role. One exception. No duplicate role to maintain forever.

Put your team on the same system as your sales

Start free, add your staff, and give each person exactly the access their job needs — no more, no less.