One login per employee, one rule everywhere: you see only your own data. Bonuses with the full calculation behind them, your shifts, an official attendance PDF and every weekly report — in one place.
Built for a multi-location retail company in Poland
Bonuses used to live in a Google Sheet shared with the whole team. One employee said they weren't comfortable with colleagues seeing their bonus — a small remark that named a real problem: personal data deserves a personal view. The portal was built to fix exactly that.
Today it's each employee's own corner of the company system: bonus history with the full commission breakdown behind every figure, their own shifts read live from the very spreadsheet the admin team maintains, an official attendance PDF produced by the same generator the HR office uses, and a searchable archive of the weekly briefings generated by the Trello reporting automation — the one described in its own case study.
Technically it's deliberately boring: server-rendered Django with Tailwind, session logins, an interface in the employees' own language, separate phone and desktop layouts, no SPA. Boring is exactly what you want from software that shows people their pay.
Sample data, real structure: this is the employee's view. Every figure on this screen belongs to the logged-in person — and only to them.
Good morning, Jan!
Bonuses
Schedule
Weekly reports
Stock search
permission group
What an employee can do
What feeds each section
The portal's job is showing people their pay — so privacy is not a feature on a list, it is the architecture.
Every personal view filters by the logged-in user. No URL manipulation can reveal another person's bonuses, shifts or reports.
Middleware routes employees to the portal and admins to the office panel — crossing over is technically impossible, not just hidden.
Extra sections appear on the dashboard only for explicit permission groups, never for every logged-in user.
Schedule and attendance PDF come from the admins' own spreadsheet and generator — the employee's document always matches HR's.
Generated startup passwords and raw commission source files are deliberately excluded from version control.
From the portal an employee can change only their e-mail address and password — nothing else is editable.
Technology: Python · Django · Tailwind CSS · Google Sheets API · PDF generation · PostgreSQL
A custom portal gives every employee a secure view of their own data — built on the systems you already run, without changing how your admin team works. Let's talk.
Discuss your project