Liferay intranet portals your employees actually open

Intranets fail for a predictable reason: they are built as a publishing site when the employee needs a working tool. Communications teams own the home page, IT owns the links, HR owns a separate system, and the employee learns within a month that the fastest route to anything is to bypass the intranet. Adoption drops, content goes stale, and three years later a new team proposes a relaunch. The fix is not a better design; it is making the intranet the place where things get done.

Liferay DXP is built for exactly that. It is a portal platform first — identity, roles, permissions, sites and personalisation are the core, not add-ons — with content management, forms, workflow, search and headless APIs on top, and an integration model that lets a single page show a leave balance from SuccessFactors, an open ticket from ServiceNow and a purchase approval from SAP, each governed by who the user is. Wipro consolidated HR, IT service requests and internal communications for 200,000+ employees across 50+ countries into one portal on this model: self-service adoption rose 75 % within six months and HR ticket resolution fell from three days to under four hours.

The second ingredient is personalisation that is actually used. ITC Infotech's intranet put supply-chain data, HR information and operational metrics on role-based dashboards — a plant manager, a buyer and an HR partner each saw a different home page — and engagement rose 70 %. Relevance is what brings people back; a news feed is not.

We are asked this in most first meetings, and the honest answer is that SharePoint is the right choice for some organisations. If you are a Microsoft 365 shop, your intranet is mostly documents and news, your users live in Teams, and you have no need to bring partners, suppliers or customers onto the same platform, SharePoint Online with Viva is already licensed and already integrated, and we will tell you so. Building a Liferay intranet in that situation is spending money to move sideways.

Liferay wins when the intranet has to be an application platform rather than a document site. Deep integration with non-Microsoft systems — SAP, Oracle, ServiceNow, custom Java services — is where Liferay's portlet and headless model is at home and SharePoint's web parts are not. Custom workflows beyond what Power Automate handles comfortably, role- and segment-based personalisation across large and diverse populations, one platform that also serves suppliers, dealers and customers as extranets, and full control over hosting — on-premise, your cloud, or in-region for data residency — all favour Liferay. So does the commercial model when populations are large: SharePoint is licensed per user through Microsoft 365, including external users beyond the guest allowance, while Liferay DXP is subscribed per instance, so 50,000 employees and 5,000 suppliers do not multiply the bill.

The usual outcome in a Microsoft shop that still chooses Liferay is both: Liferay as the front door and application layer, with SharePoint and OneDrive remaining the document store behind it, surfaced through Liferay's document-library integrations and search. We have built that pattern, and the L&T Infotech supplier portal — SAP-integrated, audit-trailed, external-facing — is the kind of workload SharePoint would have struggled with.

The test of an intranet's self-service is whether an employee can complete a task without leaving it. We integrate at the transaction level: leave requests and balances against SuccessFactors, Workday or Oracle HCM; payslips and letters from the payroll system; IT incidents and requests created and tracked in ServiceNow or Jira Service Management; expense claims and purchase approvals against SAP or Oracle; and identity from Active Directory or Entra ID through SAML or OpenID Connect so nobody logs in twice. Each integration is a versioned service layer between Liferay and the back end, not point-to-point wiring inside a portlet, which is what keeps the portal upgradeable and the integrations testable.

Where the transaction system's API is thin or slow, we put a Spring Boot service in between to cache, aggregate and enforce rules — the pattern behind the dashboards at ITC Infotech, where SAP supply-chain modules were surfaced end to end, and at Xebia, where Jira, GitHub and CI/CD dashboards were combined into one developer portal that cut context-switching by 40 %. For engineering-heavy organisations, InfoBeans' resource-management portal — live availability, skill matrices, timesheets and automated billing for 500+ engineers — shows how far an intranet can go once it is treated as an application platform.

Communications on a Liferay intranet are targeted, not broadcast. Content is authored in content pages and fragments that business teams edit without a developer, published through an approval workflow, and shown by segment — role, location, business unit, language, device — so a Riyadh sales team and a Bangalore delivery centre see different front pages from the same site. Multi-language sites, translation workflows and country sub-portals on a shared component library are standard; Wipro's 50+ country portals were built that way.

Knowledge is where most intranets are weakest and where Liferay's document library, metadata and Elasticsearch integration are strongest. Capgemini's knowledge-management portal — role-based access, document versioning, full-text search across practice areas — cut document retrieval time by 80 % and gave client project dashboards that raised stakeholder satisfaction scores by 40 %. KnoVarth's learning-experience platform added personalised learning paths and knowledge discovery on the same foundation, scaling to 10,000+ concurrent users. Increasingly, the search box becomes an assistant: a retrieval-augmented assistant that answers from the same policies and documents, with citations and the same permissions, sits naturally inside the intranet people already open.

We design an intranet around the ten tasks employees do most, found by interviewing them rather than the steering committee, and we make each one shorter than the alternative — fewer clicks than email, faster than asking a colleague. Personalisation follows from that: the home page for a role is the tasks that role does, with news and campaigns beside them rather than instead of them. Mobile is not a separate project; the portal is responsive from the first sprint and, where field or plant staff need it, the same content and services are exposed through Liferay's headless APIs to a companion app.

Then we measure. Liferay's analytics and our own dashboards track active users by role and location, task completion, search queries with no result, content nobody reads and the tickets that still arrive by email. The first three months after launch are run as a product, not a project: weekly reviews of those numbers, content pruned, dead ends fixed, the next integrations prioritised by demand. That is how Wipro reached 75 % self-service adoption in six months and why ITC Infotech's engagement went up rather than down after year one.

As a guide from our projects: a focused intranet for one organisation — communications, self-service against two or three back-end systems, knowledge and search, SSO — goes live in 12–20 weeks from kick-off, delivered in sprints so communications can start publishing before the integrations finish. A multi-country or multi-company digital workplace with many sub-portals, languages, integrations and custom applications is a programme of six to twelve months, released in phases by region or by capability.

Five things set the cost. The number and depth of integrations, because a leave balance shown on a page and a leave request completed on it are different amounts of work; the number of sub-portals, languages and brands; custom applications — resource management, supplier onboarding, learning paths — beyond configuration; migration from an existing intranet, whether that is SharePoint content, a legacy CMS or a Liferay 6.x portal that needs upgrading; and hosting and licensing — Liferay DXP subscription per instance, or the community edition where support terms allow, on your servers, AWS, Azure or Liferay's cloud. We quote discovery as a fixed fee and the build as a fixed price for the agreed scope; tell us the systems and populations involved and we will send a bracket within a week.

Our intranet and employee-portal work clusters where the workforce is large and the systems are many: IT services and consulting firms — Wipro, ITC Infotech, Capgemini, Xebia, InfoBeans, Fulcrum — where the portal is the operating tool for delivery as much as for HR; banks and financial institutions, where staff portals carry maker-checker workflows and regulated content; manufacturers with plant, dealer and supplier populations on one platform; and public-sector and education bodies with programmes, institutions and staff to serve. The same platform serves the extranet — suppliers, dealers, partners, customers — which is usually the second phase and the reason Liferay was chosen over a document-centric tool.

If you already have a Liferay intranet on an old version, the conversation is different and shorter: an upgrade to DXP 7.4 with the adoption work folded in is usually the better investment than a relaunch. The wider practice — customer portals, headless integrations, the engineering principles and the full case-study list — is on the Liferay DXP services page.