Employee Self-Service Portal. @employee-portal

When employee requests run through email and shared drives, HR and operations become a routing desk — and employees wait days for answers the systems already hold. The Employee Self-Service Portal sprint builds a secure portal for a defined set of workflows: leave and requests, payslips and documents, policy and information lookup, onboarding tasks — whichever set your scoping fixes.

The finish state is employees completing those workflows without raising a ticket: signed in through your identity provider, seeing only what their role allows, with requests flowing into the systems of record rather than an inbox. The portal is deliberately scoped — a defined workflow set done properly beats a portal that promises everything.

SSO & Employee Identity

Single sign-on against your identity provider — Entra ID, Google Workspace, or Okta — with role- and department-based access and automatic deprovisioning when people leave.

Self-Service Workflows

The scoped workflow set built end to end — request forms, approvals, status tracking — so each one completes in the portal, not around it.

Documents & Information Hub

Secure access to personal documents and company information — policies, contacts, announcements — with search and per-audience visibility.

HR System Integration

Two-way integration with your HRIS and payroll systems in scope, so the portal reads from and writes to the systems of record instead of duplicating them.

1. Scope — Pick the workflow set by volume and pain, map the systems of record, and fix access rules and success measures.
2. Build — Build portal, workflows, and integrations; pilot with one department and tune from real usage.
3. Handover — Company-wide rollout with comms support, admin training, and documentation.

The Employee Self-Service Portal is a menu item on the Scrums.com delivery catalog, available at every plan tier. Add it to your plan backlog and your delivery team schedules it like any other item — scoped, tracked, and reported through the SEOP. See Delivery Plan Tiers.

Does this replace our HRIS?

No — it sits in front of it. The HRIS stays the system of record; the portal gives employees one place to interact with it and the surrounding processes.

Which workflows should go first?

The ones generating the most tickets — typically leave, document requests, and policy questions. Scoping ranks your candidates by volume and effort so the first release removes real load.

Can we add approval-heavy processes later?

Yes. Simple approvals are in scope from the start; complex multi-step approval chains are the Workflow Approval System, which plugs into the same portal as a follow-on item.