GoldenrozBook a call

Employee self-service portal: what it should include and what it connects to

An employee self-service portal, or ESS portal, is a signed-in site where employees handle their own HR and administrative tasks: view payslips, request leave, update personal details, submit expenses and open IT requests. Its value comes from its connections to payroll, HR, the user directory and the ERP. Start with the three or four requests that create the most manual work and add the rest in phases.

A gold sphere set into a structure of stacked navy and white cubes.

What self-service means in practice

In a company without a self-service portal, an employee who wants a day off asks a manager by message, the manager forwards it to HR, and HR types it into the attendance system. The same path repeats for an address change, an employment confirmation letter, a payslip copy and a new laptop.

A self-service portal removes the retyping. The employee enters the request once, the right person approves it, and the result is written to the system that needs it. HR stops being a data entry service and the employee can see where the request stands.

An HR portal of this kind is one of the most common internal systems a company runs, and one of the easiest to judge: either people use it every week or they do not.

What an employee self-service portal should include

Personal data

  • Profile: contact details, address, emergency contact, bank details where policy allows
  • Change requests for those fields, with approval where needed
  • Documents on file: contract, signed policies, certificates

Pay and time

  • Payslips and yearly tax forms, from the payroll system
  • Leave balance, leave requests and sick day reports
  • Attendance record and corrections
  • Team calendar showing who is away

Requests and forms

  • Expense reports with receipt upload
  • Travel requests, which connect to travel management software where one exists
  • Equipment and access requests to IT
  • Employment confirmation letters and other standard documents
  • A general request form for everything without a dedicated one

Manager self-service

  • A single list of items waiting for approval
  • Team overview: leave, attendance, open requests
  • Starting processes: a hiring request, a role change, an offboarding

Company content

  • News, policies and the directory, as in any intranet. Our post on what an intranet is covers that layer.

Not every company needs every item. A portal with four things that work is better than one with twenty links to other systems.

What it connects to

The portal holds little data of its own. Its job is to show and update data that lives elsewhere. The connections decide both the value and the cost.

System What the portal reads What the portal writes
User directory (Microsoft Entra ID, Active Directory or similar) Identity, department, manager, groups Usually nothing, or profile fields
HR system Employee record, role, start date Approved changes to personal details
Payroll Payslips, tax forms Usually nothing
Time and attendance Balances, attendance Leave requests, corrections
ERP or finance Cost centres, budgets, suppliers Approved expenses and purchase requests
IT help desk Ticket status New tickets
Document storage Policies and personal documents Signed forms
Email and chat Nothing Notifications and approval prompts

Three points about integrations are worth settling early.

One sign-in. The portal should accept the work account people already have. A separate username is the fastest way to lose usage.

The manager chain has to be right. Approvals route by the manager field in the directory or HR system. If that data is wrong, every approval goes to the wrong person. Cleaning it is often the first task of the project.

Read first, write later. Showing a leave balance is low risk. Writing a leave record into the attendance system needs validation, error handling and a way to correct mistakes. Plan the read integrations for phase one and the write integrations after them.

Where a system has no API, there are still options: a scheduled file export, a database view, or a small service on a server inside the network. Shai’s work at an industrial company with about 400 users included integrations of this kind on an on-premises server with Docker, SQL Server and Postgres.

Permissions and privacy

A self-service portal shows salary and personal data, so access rules are part of the design and not a setting to tune later.

  • An employee sees only their own records
  • A manager sees their direct team, and only the fields a manager needs
  • HR roles are split: not everyone in HR needs payroll data
  • Every view of a payslip and every change to a record is logged
  • Sensitive fields such as bank details change only with a second confirmation
  • Access ends the moment the account is disabled, which ties the portal to offboarding

Check which privacy and employment rules apply in each country where you have staff before deciding what the portal stores. In most designs the portal should store as little as possible and fetch personal data from the source system on request.

Buy, configure or build

Route When it fits What to watch
The self-service module of your HR or payroll product You already own the product and the module covers your needs Limited to that vendor’s data and screens
A dedicated portal product Standard needs, short timeline Recurring subscription, limits on custom processes
SharePoint with Power Automate Company is on Microsoft 365, needs are mostly forms and approvals Personal data from payroll needs custom development
Custom-built portal Several source systems, company-specific processes, on-premises requirement or a high subscription to replace Needs an internal owner and a maintenance budget

If your HR product already has a self-service module that people would accept, use it. A custom portal earns its cost when the data sits in several systems that no single vendor covers, or when the current subscription is large relative to what the portal does. The arithmetic is in our post on build vs buy software.

For forms and approvals on Microsoft 365, see what Power Automate is.

How to phase the build

A portal launched all at once is hard to test and hard to adopt. A phased plan:

  1. Phase 1: identity and read-only. Sign-in with the work account, profile, directory, leave balance and payslips. This proves the integrations with the directory, HR and payroll.
  2. Phase 2: the top requests. Leave requests and one or two high-volume forms, with approval routing and notifications.
  3. Phase 3: manager view. The approval list, team calendar and team overview.
  4. Phase 4: the wider set. Expenses, travel, equipment, document requests, and the connection to employee onboarding automation so that a new hire gets a portal account and a task list on day one.

Each phase goes to real users before the next begins. Usage in phase one tells you what to build in phase two.

How to tell whether it works

Measure three things from the first month, and compare them with the count you took before launch.

  • Share of requests through the portal. Leave requests submitted in the portal against those still sent by email or on paper. If the old channel stays open, people keep using it, so set a date after which HR accepts the request only through the portal.
  • Time from request to decision. The portal records both timestamps. Long waits usually point to one approver or to a wrong manager field.
  • Weekly active users. People who signed in at least once in the week, split by office and frontline staff. A gap between the two groups is normally a sign-in or device problem and not a lack of interest.

Numbers like these also settle the question of what to build next. A form nobody uses is removed. A request that still arrives by email in volume gets its own form.

A requirements checklist

  • The ten requests HR and IT receive most often, with monthly volume
  • The system of record for each piece of data
  • Whether each system has an API, a file export or neither
  • The source of the manager chain, and how accurate it is
  • Who may see what, by role
  • Which staff have no desk or no company email, and how they sign in
  • Languages and text direction
  • Where the portal must run: cloud or the company’s own servers
  • Who owns the portal after launch
  • How success is measured: requests through the portal against requests by email

What to do next

Count last month’s HR and IT requests by type. The top three are your phase one, and the count gives you a baseline to measure against after launch.

We design and build owned portals, including the integrations, through our employee portal development service. Shai does the scoping and the engineering. Projects start at $25,000 at a fixed price per phase, and the code belongs to the company.

Questions buyers ask

What is an ESS portal?

ESS stands for employee self-service. An ESS portal is a private site or app where employees complete HR and administrative tasks themselves, such as viewing payslips, requesting leave and updating an address, without sending an email or a paper form to HR.

What is the difference between an ESS portal and an intranet?

An intranet publishes content that is the same for everyone: news, policies, a directory. An ESS portal shows data that is personal to the signed-in employee and lets them act on it. Many companies combine both in one employee portal.

What is manager self-service?

Manager self-service, or MSS, is the manager's side of the same portal. A manager sees the team's requests, approves or rejects leave and expenses, views the team calendar and starts processes such as a hiring request or a role change.

Does an employee self-service portal replace the HR system?

No. The HR and payroll systems remain the systems of record. The portal is a front end that reads from them and sends approved changes back. Replacing the HR system is a separate and much larger decision.

What should be built first in an employee portal?

Sign-in with the work account, the employee's own profile, and the two or three requests with the highest volume, usually leave, payslip access and one general request form. These prove the integrations and give people a reason to return every week.

Written by

CTO and technology partner

Shai leads the technology side: business software, SaaS and mobile apps, payments and escrow systems, Postgres security, AI agents built with Claude Code and MCP, and IT and infrastructure projects with senior infrastructure engineers.

Keep reading

Talk to the person who will do the work

One hour, no sales team. You talk to Daniel or Shai, we look at your account or your product, and you leave with a clear next step.

Or send the details

Book a 1-hour consultationWhatsApp us