From Fragmented Portals to a Single Front Door: Architecture, UI/UX, and Security Design for a Multi-Department Enterprise Service Center

Abstract

Enterprises increasingly replace scattered departmental portals with a single digital front door, yet departments such as IT, HR, Facilities, Legal, and Procurement differ in their user populations, service taxonomies, content models, and access requirements. The technical challenge is therefore not only how to build any one department's workflow, but how to design a portal architecture that supports these structurally different needs without recreating the departmental silos and portal sprawl that a unified portal is meant to eliminate. This case study describes the design and in-house deployment of a multi-department Employee Service Center, built on Service Portal/Employee Center Pro, that replaced a legacy single-purpose Service Portal. We outline the architectural decisions that allowed one shared portal to serve departments with divergent security postures. These include taxonomy design and content curation to prevent cross-contamination of departmental catalogs, and a widget and Page Designer approach in which each department owns its presentation-layer components without modifying shared platform code. They also include a security model based on SSO federation (Okta/LDAP), role- and ACL-based content scoping, and authenticated-only content gating. On the fulfilment side, we discuss Agent Workspace and Service Operations Workspace with the Next Experience UI as the operational counterpart to the employee-facing portal. We then show how third-party AI search and virtual-agent widgets (such as Aisera and Glean) can be embedded in the portal shell, extending a unified portal without vendor lock-in on the core platform. Organizational outcomes include delivery at zero additional vendor cost, consolidation of five separate service channels into one entry point, and reusable design patterns for other organizations pursuing portal unification.