ServiceNow HR Profile Explained

What Is an HR Profile?

An HR profile in ServiceNow is a data record storing information about a person relative to their work life. It connects to tables tracking employment details, assignments, performance data, and organizational position. An HR profile is not the same as a user record; a user record grants access to the ServiceNow platform, while an HR profile holds employment and organizational context.

In plain terms: if someone works for an organization, an HR profile exists or should exist to represent them. The profile does not determine whether they can log into ServiceNow. Instead, it provides data for other processes: absence tracking, organizational charts, expense routing, or skills management.

Where HR Profile Lives in the Platform

ServiceNow stores HR profile data in the HR profile table, sn_hr_core_profile, which the HR application provides. This table can be populated manually, synchronized from external HR systems via data import, or managed through HR module workflows. The record contains fields for name, email, phone, hire date, status, and custom fields unique to each organization.

Related tables extend HR profile capability. The cmn_emp_profile_expertise table tracks skills. The cmn_emp_profile_reporting table manages reporting lines. The sysapproval_approver table links approvers for workflows. These relationships allow complex behaviors: when a request needs approval, ServiceNow looks up the approver’s manager from their HR profile reporting line rather than requiring hardcoded approver assignments.

A Worked Example

Imagine a request for budget approval arrives in ServiceNow. The requestor is a program manager in the Product organization. The request workflow needs a manager’s approval. The system looks up the requestor’s HR profile, reads the report_to field, and routes approval to that person. If the HR profile is missing or reporting line data is stale, approval may route incorrectly—sending requests to a departed manager or skipping appropriate reviewers.

When that manager approves, the request moves to procurement. Procurement policy requires approval from a director if the request exceeds a threshold. Again, ServiceNow uses HR profile data, this time looking up organizational hierarchy to find the relevant director. This cascading logic works only if HR profiles remain current.

Common Misunderstandings

Many teams confuse HR profile with user account. An organization might assume that creating a user account creates an HR profile, or vice versa. In reality, these are separate. A user account (sys_user table) is necessary to access the platform. An HR profile (sn_hr_core_profile table) is necessary for approval routing, organizational charts, or HR-specific workflows. Some organizations have users with no HR profile, and others have HR profiles with no user account (for example, contractors or advisors who participate in approvals but do not log into the platform).

Another misconception: updating a user record’s name or email automatically updates the HR profile. Depending on integration configuration, changes may flow one direction, both directions, or neither. Some organizations maintain two sources of truth; ServiceNow acts as a read-only view. Others use ServiceNow as the authoritative source and push changes back to external HR systems.

Related Concepts

HR profiles connect to organizational charts, which visualize reporting relationships. They relate to absence management, where time off accruals depend on employment status in the HR profile. They support skills management, where employee expertise stored in related tables informs resource allocation. Understanding HR profiles requires familiarity with these adjacent concepts and how data flows between them.

Deciding which HR profile fields to govern first

Many teams try to clean every employee attribute before they switch anything on, and that approach often stalls for months. A better starting point is to list the downstream processes that will read the profile, then govern only the fields those processes depend on. Approval routing needs a reliable manager link and an active status. Organization charts need a job title, a department and a location. Skills matching needs the skills table kept current. Each process has a different owner and a different tolerance for error, so the governance effort should follow that map rather than the alphabetical list of columns.

Field group	Process that reads it	Typical owner	What breaks when it is stale
Status and employment dates	Access to requests, leaver workflows	HR operations	Former staff keep receiving tasks
Manager and reporting line	Approval routing, escalations	HR business partner	Approvals wait on someone who has moved on
Department, cost center, location	Budget approvals, org charts, facilities requests	Finance or HR systems team	Requests route to the wrong budget holder
Skills and certifications	Resource assignment, support routing	Line managers with HR review	Work goes to people who no longer hold the skill

The order of this table matters. Status and reporting line sit at the top because a wrong manager link produces the most visible failure, which is a request sitting in an inbox nobody monitors. Skills come last because a stale skill often causes slow routing, not a dead end, and it is easier to correct with a periodic review.

A sequence for standing up HR profiles without breaking approvals

The safest rollout keeps the existing approval path running while the profile data is tested in parallel. Work through the steps below in order, and do not skip the comparison stage even when the source system looks clean.

1. Export a sample of active approvers and their current manager links from the authoritative HR system, then compare that sample with the profile records in ServiceNow.
2. Agree a single source of truth for each governed field. Write it down in the data ownership register, including which direction changes flow and what happens when the two systems disagree.
3. Run the import in a sandbox or a non-production instance and review the rows that were created, updated and rejected. Check especially for people who appear twice because a name changed.
4. Switch one approval flow to use the profile lookup, leaving the others on their old logic, and watch a full business cycle before moving the next flow.
5. Set up a standing exception report of profiles with no manager, a manager who is inactive, or an end date in the past, and assign a named person to clear it.

Signs the profile data is not doing its job

A profile problem rarely announces itself as a profile problem. It shows up as a workflow that stalls, a manager who says they never received an approval, or an org chart that shows a senior leader with no reports. When you investigate, the question to ask is whether the workflow read a profile field that was empty, out of date or pointing at a deactivated record. Logging the lookup result, not just the final approver, makes these cases much faster to diagnose.

Look also for duplicate people. When a contractor is converted to an employee, the old profile and the new one can both remain active, and approvals then split between two identities. Reconciling identities on a regular cadence is more reliable than waiting for a user to complain.

Leavers, contractors and people who should not have a profile

The lifecycle of a profile deserves its own rules. The lifecycle event guide describes how joiner and leaver triggers can drive these changes. A leaver’s profile should not simply be deleted, because historical approvals and assignments still reference it. A common approach is to deactivate the profile, close its employment dates, and reassign any open approvals to a delegate chosen by the leaver’s manager. Contractors are a separate case. Some need a profile so that they can appear in approval chains or in a resource plan, but they should never be treated as employees in headcount or leave calculations. Decide that boundary before the first import, since changing it later means reworking every report built on top of it.

There are also cases where an HR profile is the wrong tool. If the goal is only to let a person log in and raise tickets, a user record is enough. Creating profiles for everyone who has ever touched the platform adds reconciliation work without adding routing value.

When not to build the profile layer yet

Hold off on the profile layer if the authoritative HR system cannot yet produce a reliable manager link, or if nobody has agreed who corrects a wrong one. In that situation, ServiceNow will faithfully route work to the wrong place, and the platform team will be blamed for it. A narrower first step is to keep approvals on their current logic and use the profile data only for read-only views such as an org chart. That gives the business a visible improvement while the governance catches up.

Common questions about HR profile operations

Should contractors and advisers get an HR profile?

Only if they must appear in approval chains, resource plans or org views. Give them a distinct employment type so they are excluded from headcount and leave logic. Mixing them with employees is a common cause of inflated reports.

Why does an approval still reach someone who left last month?

Often because the profile was deactivated without changing the reporting line on the requests already in flight, or because the new manager was never linked to the team. Check open approvals for the leaver first, then review the leaver checklist so that delegates are set before the final day.

How do we decide which system wins when HR and ServiceNow disagree?

Assign authority per field, not per system. The HR system may own the reporting line while ServiceNow owns the skills list. A written field-level rule resolves most disputes before they reach a committee.

Can we roll out profiles one department at a time?

Yes, if approval flows for the other departments keep their current logic, and if the employee-facing side is ready as well; the employee center guide covers the employee-facing side. Staged rollout works best when the first department has clean data and an engaged manager who will report problems quickly.

Next step

Deciding how far HR profile data should reach into approvals and org views is worth settling with HR operations and platform owners before any records are loaded. The HR service delivery overview on the HR Service Delivery library shows how profile data fits the wider HR workflows.