Skip to content

System type 06 / 11

Internal portals

Employee services in one place: requests, letters, leave and announcements, on desktop and mobile.

When you need it

Three signs a process has outgrown its tools.

  1. 01

    Employees don't know where to file a request

  2. 02

    Repeated requests consume HR time

  3. 03

    No way to follow a request

What it contains

The modules the system is built from.

A possible scope, not a fixed list: we choose with you what is built first and what waits.

  1. M01Employee home
  2. M02Service catalogue
  3. M03Requests and status
  4. M04Leave
  5. M05Letters
  6. M06Announcements
  7. M07Profile
  8. M08Mobile interface
Who it is for

A system tied to a real operating problem.

For organizations that want a clear employee entry point for services, requests and relevant information instead of scattering them across email, messages and separate systems.

U01

Employee services in one place

Forms, requests and clear status tracking according to the employee's permissions.

U02

Portal by role and function

Employees see what concerns them while managers or HR receive different tasks and permissions.

U03

Focused internal information

Present links, content and services relevant to the user's role rather than generic pages that ignore role differences.

Workflow

From process to an operational system.

The order changes by project scope; this is the structure we use to make decisions and ownership explicit before expanding.

  1. 01Define the services employees can access
  2. 02Map each service to roles and permissions
  3. 03Design entry, status and notifications
  4. 04Connect requests to their internal workflows
  5. 05Roll out the portal gradually around the highest-use services
Integrations
  • The portal can connect to existing HR or service systems through APIs when available
  • Keep the original system of record clear when surfacing data from other systems
  • Combine PeopleHub and ServiceDesk service foundations in one experience depending on project scope
Governance & value

What should remain clear after launch.

Security & control
  • Role- and permission-based personalized experience
  • Do not expose services or data outside the user's scope
  • Record important user actions where required
  • Arabic and English interface support
Business value
  • Reduce time spent finding the right form or owner
  • Clearer status for internal requests
  • One entry point instead of fragmented services
Why VANTERA
  • PeopleHub provides a foundation for employee services
  • ServiceDesk supports requests, queues and tracking
  • The portal can connect to HR and workflow solutions instead of becoming an isolated front end
Related paths
Questions before starting

Clear answers before the analysis session.

Q01Is an employee portal a full HR system?

Not necessarily. A portal is an entry point for authorized services and information and can connect to existing HR systems or expand according to project scope.

Q02Does every employee see the same content?

No. The experience can vary by role, department, permissions and service scope.

Q03Can we start with a small set of services?

Yes. High-use services can launch first, with additional workflows added gradually.

Two ways to start

From an approved product foundation, or from scratch.

How we workSix clear phasesDetails
  1. 01Process analysisCurrent process map
  2. 02Screens and rulesInteractive prototypes
  3. 03Phased developmentReview environment
  4. 04Integration with your systemsIntegration map
  5. 05Launch and trainingData migration
  6. 06Operation and supportMonitoring
Before requesting a proposal

Tools to clarify the decision and scope.

Start a project

Discuss internal portals with our analysis team.

An intro session with our analysis team to review your current processes and scope the first system.