Walk through Tenure
10 of 18 screens are live in the demo. Everything else is visible but marked, with a reason — nothing is a dead link.
How to sign in
The demo has its own login because that is part of the product. These accounts are fictional, the passwords are deliberately fake, and each one sees a different slice of the platform — so it is worth signing in as more than one.
| Role | Password | What they can see | |
|---|---|---|---|
| TENANT_ADMIN | [email protected] | tenure-demo | Every module for this tenant, plus tenant settings and the audit log |
| HR_MANAGER | [email protected] | tenure-demo | People, attendance and leave, and the org structure — not tenant settings |
| MANAGER | [email protected] | tenure-demo | Their own team, the approvals inbox and leave — no payroll and no settings |
| EMPLOYEE | [email protected] | tenure-demo | Their own record, leave balance and documents only |
What to try first
- Open a tenure timeline and watch counted service resolve: calendar days minus the periods that do not count
- Change the vesting cliff in Tenant Settings, then reopen a timeline — the marker moves and nothing needed recalculating
- Approve a leave request, then open the Audit Log and find the entry you just created
- Switch role to EMPLOYEE in the demo bar and watch the sidebar shrink to what they may see
- Open Roles to see all ten the platform defines, and why six cannot appear in a single-tenant demo
- Click a greyed item such as Payroll to see what it does in the real platform
Every screen, and whether it is in the demo
Grouped the way the real platform groups them. A screen marked not in the demo is still visible in the demo's navigation — clicking it explains why and offers a walkthrough, rather than doing nothing.
Dashboard
Headcount, the approvals backlog and who is approaching a vesting cliff — every figure derived from the employee records.
Recruitment, pipeline, scorecards and interview rooms
Requisitions through to interview rooms, scorecards and the public careers page.
Interview rooms need WebRTC and a signalling server; the rest of the module is not seeded in this demo.Employees
The directory, with counted service computed per row — which is what makes sorting on it meaningful.
Employee record
One person: their service events as an append-only timeline, leave history, manager and direct reports.
Tenure timeline
The signature screen. Joining date to today with the vesting cliff marked and excluded periods cut out of the bar, plus the subtraction in the open.
Onboarding and offboarding
Joiner checklists with document collection, and the exit workflow with handover sign-off.
Both need server-side document storage and the background queue that generates contracts and letters.Attendance & Leave
Who is in, who is off today, what is booked this month and the average balance — all derived from approved requests.
Leave Requests
The approvals inbox. A rejection requires a reason the employee can read, enforced in the domain rather than the form.
Payroll and Payslips
Pay runs, employee payments and payslip generation.
Payroll needs statutory tables and a pay-run engine. Producing a payslip from invented data would misrepresent it.Performance, review cycles and learning
Goals, review cycles with peer feedback, the course catalogue and personal learning paths.
The LMS needs media storage; the review module is built but not seeded in this demo.Engagement, events, kudos and service desk
Announcements, the events calendar, the kudos feed and the internal ticket queue.
Built in the real platform; this demo does not seed data for them.Integration keys, form builder, payload mapper, webhooks
The scoped client API, a drag-and-drop form builder, field mapping and outbound webhooks with retry.
Keys authenticate a real API and webhooks run on the BullMQ queue — a browser-only mock has neither.Departments
The org structure every record hangs off, with headcount counted from the records rather than stored.
Roles
All ten roles the platform defines, their scope, and why six of them cannot be shown by a single-tenant demo.
Divisions, ticket types and sub-categories
The rest of the org taxonomy: divisions above departments, and the service-desk category tree.
Built in the real platform; this demo does not seed data for them.Tenant Settings
Per-organisation configuration. Changing the vesting cliff here visibly recomputes every tenure timeline.
Audit Log
Append-only over privileged actions. Approve a leave request and the entry appears — it is a projection of what happened, not a parallel list.
White-Label Theme, SSO & Database, Raised Requests
Per-tenant branding, SAML/Entra/SCIM configuration with bring-your-own-database, and the super-admin request queue.
SSO needs a real identity provider, and the other two only mean something with more than one tenant.Good to know before you open it
- It runs entirely in your browser. There is no server, and nothing you type leaves the page.
- Your edits persist across a refresh, and Reset data in the demo bar puts the sample data back.
- A guided tour starts on your first visit and can be replayed from the demo bar.
- It works on a phone as well as a desktop.