The modules
Seven modules. Each owns its data and its access rules, so a plan can switch one on without touching anything else, and switching one off hides it everywhere at once — in the navigation, in the pages, and in the actions behind them.
People
StarterTeamBusiness
- What it does
- Employee records, the directory, departments, offices, reporting lines and the org chart.
- What it stores
- Names, contact details, the identifiers your country needs, job history with its own effective dates, documents and their expiry dates, family members, emergency contacts, assets held.
- Who can see it
- Everybody sees the directory. A record’s sensitive parts follow the rules on the roles page — and nobody changes their own job, department or manager.
Leave
StarterTeamBusiness
- What it does
- Leave types and policies you write, balances that follow from them, requests, approvals and the absence calendar.
- What it stores
- Requests, decisions with who made them and when, adjustments, and per-office holidays.
- Who can see it
- People see their own and their team’s. A decision is a row that cannot be edited afterwards, only superseded.
Policies
TeamBusiness
- What it does
- The handbook, published with versions, acknowledgements and optional quizzes.
- What it stores
- Sections, versions, who acknowledged which version and when.
- Who can see it
- Everybody reads it. An acknowledgement cannot be entered on somebody else’s behalf.
Payroll
TeamBusiness
- What it does
- Pay components, salary packages, payslips, batches with an approval chain, off-cycle runs, loans and provisions.
- What it stores
- Salaries, transactions, payslip lines, bank details and loan schedules.
- Who can see it
- Pay needs a capability granted to a named person. Being an administrator is not enough, which is the point.
Work logs
StarterTeamBusiness
- What it does
- Projects, the activities your company logs against them, targets, and the dashboards that follow.
- What it stores
- Entries against a project and an activity type, with the fields your company defined.
- Who can see it
- Only the person whose day it is writes an entry. A team lead reads their own people’s; a manager reads their department’s.
Wellbeing
StarterTeamBusiness
- What it does
- An anonymous board for how people are actually doing, open to whichever offices you choose.
- What it stores
- Posts and reactions, with no author column at all.
- Who can see it
- Nobody can trace a post to a person — not an administrator, not us. That is a property of the schema rather than a promise.
Attendance
StarterTeamBusiness
- What it does
- Punching in and out on the web, on a phone or on a terminal at the door, with shifts, shift swaps between colleagues, overtime and timesheets.
- What it stores
- Punches with their origin, corrections and who made them, shift assignments, overtime requests.
- Who can see it
- Employees clock; they cannot rewrite the clock. Every correction records the hand that made it, and a swap two people arrange is not settled until whoever runs the rota agrees it.
Hiring
TeamBusiness
- What it does
- Openings, candidates, the stages your company puts them through, interviews with scorecards, a public careers page for the vacancies you choose to advertise, and the offer that becomes an employee record.
- What it stores
- A vacancy and what it asks for, a candidate’s contact details and CV, every stage change with who made it, interview panels and their scorecards, and the offer.
- Who can see it
- Closed by default, which no other module is. A scorecard is its author’s until they submit it, so a panel cannot read each other before writing. Whoever runs the company sees everything; the person who owns an opening sees that opening and its applications; somebody on a panel sees only what they are interviewing for. A salary band is pay, and answers to the pay rule.
Ask Staffena
TeamBusiness
- What it does
- Answers questions about this product — where a thing lives, what a screen does, whether you may do something — and hands the conversation to a person when it cannot.
- What it stores
- The questions asked, whether an answer was found and whether it helped. No employee data of any kind: it reads this product’s documentation and the asker’s own role, and nothing else. The questions stay inside your company — Staffena sees counts, never what anybody typed.
- Who can see it
- Whoever you give it to. Asked how many days somebody has left, it points at the screen rather than fetching a number — it has no way to fetch one.
Features
A module is a subject; a feature is a capability inside one. Plans differ by both, and the list below is the one the server checks — not a summary of it.
- More than one office
- Offices with their own timezone, working week and holidays.
- Two-step leave approval
- A manager decides, then HR commits — rather than one step.
- Payslips and advances
- A monthly run, payslips people can read, advances and claims.
- Batches, off-cycle pay and provisions
- Batches with an approval chain, off-cycle runs, provisions and encashment.
- Approval routes you configure
- Who decides what, in an order the company writes itself.
- Importing a spreadsheet
- Four hundred people and a spreadsheet, checked before anything is written.
- Fields of your own
- The things your country or your industry asks for and we did not think of.
- Building your own dashboards
- Cards somebody arranges, and widgets they build from your own figures.
- Shifts and rosters
- Patterns, rosters and who is on which one.
- Tasks HR assigns
- Something HR asks somebody to do, with a due date and a queue.
- Reports
- Balances, the payroll register, headcount movement, and the file for your bank.
- Excel and PDF downloads
- A workbook and a printable file, rather than only a CSV.
- Audit history beyond a year
- The trail kept past twelve months, for an auditor who asks.
- The API
- Another system reading and writing yours, with a key of its own.
- Webhooks
- A call to your system the moment something happens in this one.
- Openings, candidates and the pipeline
- Vacancies, candidates and the stages between them, ending at an offer that starts somebody’s first week.
- Ask Staffena, the in-product assistant
- A question answered in the terms of the asker’s own role, from this product’s documentation and nothing else.
- Scoring a CV against an opening
- A CV read against what an opening asks for. Advisory, never a decision, and blind to the candidate’s name.
- Single sign-on
- Signing in with the identity provider the company already uses.
Which tier includes what is on the pricing page.