ShiftSync Platform
Multi-tenant workforce SaaS: scheduling, attendance, and team operations
Overview
ShiftSync is a company product from SISEO Digital Solutions for multi-tenant workforce operations. Each tenant plans shifts from templates and tags, assigns staff, publishes schedules, tracks clock-in/out and breaks, manages leave with approvals and documents, and keeps teams aligned with announcements, notifications, and chat. Owners and managers run the admin portal; employees use a focused portal for their shifts, time, leave, and alerts. The source is private; this case study covers the product and the work I shipped with the Sri Lanka team.
- Role
- Full stack developer
- Team
- Sri Lanka developer team (SISEO Digital Solutions)
- Timeline
- Dec 2025 – May 2026
- My contribution
- Full-stack delivery on the Sri Lanka team across admin settings and operational flows: departments, tags, shift templates, shift create/publish APIs, notification settings and leave/shift notification events, WebSocket broadcast triggers, EN/DE localization, and mobile/PWA polish. Private commercial codebase.
Problem
Companies needed one tenant-isolated system where shift plans, worked time, leave, and payroll-ready records stay consistent, with live updates when schedules change.
- Tenant isolation for many companies on one product
- Shift templates, assignments, publish/close, and clock entries that agree
- Leave rules, balances, and approvals without breaking attendance numbers
- Real-time notifications and chat so staff see changes without refreshing spreadsheets
What ShiftSync does
Admins set up departments, teams, tags, and templates, then create and publish shifts. Employees clock time, request leave, and follow notifications. Soft-delete/restore covers shifts and clock entries. Subscription and billing status sit on the tenant.
- Multi-tenant organisations with plans and billing status
- Shift templates (single and compound), tags, departments, and teams
- Shift instances: plan, assign, publish, close, reopen, and deleted-shift recovery
- Clock entries and breaks with admin edit, delete, and restore
- Leave types, rules, balances, document uploads, and approval history
- In-app notifications, Web Push paths, announcements, and direct chat
Who uses it
Roles are owner, manager, and employee. Owner and manager work in the admin portal for people, shifts, time tracking, leave, reports, and settings. Employees get their own portal for assigned shifts, clocking, leave, and notifications.
- Owner: full tenant admin, including settings and operational oversight
- Manager: day-to-day scheduling, attendance, leave, and team coordination
- Employee: own shifts, clock-in/out, leave requests, availability, and alerts
Technical decisions
Next.js owns the portals and many tenant-scoped API routes. A NestJS service handles real-time WebSocket fan-out. Prisma models keep tenant_id on operational tables. My work focused on shipping admin settings and notification paths that stay correct under live updates.
- Tenant-scoped Prisma models for users, shifts, clock entries, leave, and notifications
- NestJS WebSocket gateway for shift, clock, leave, stats, and notification broadcasts
- Admin departments, tags, and template settings with soft-delete/restore tables
- Shift create/update/publish flows that trigger tenant WebSocket updates
- Notification settings and leave/shift event localization (EN/DE)
- Service worker / PWA install paths and mobile filter polish for field use
- Docker and GitHub Actions pipelines publishing GHCR images per environment
What changed
Tenants can run scheduling, time tracking, and leave in one product, with live updates instead of status chasing in chat threads.
- Published shifts and clock changes reach the right roles over WebSocket
- Leave and shift events respect notification preferences and locale
- Admin settings for departments, tags, and templates stay consistent with shift assignment
Stack
Next.js, TypeScript, NestJS (WebSocket), Prisma, PostgreSQL, NextAuth, Redux Toolkit, Tailwind CSS, Docker, GitHub Actions, EN/DE i18n.
More projects
Explore other work in the portfolio







