The HRSD demo handled the happy path beautifully. The first real onboarding case in production touched five teams, hit a regulatory question about data residency, and exposed an ACL gap that left compensation details visible to the IT support group. The HR Service Delivery application is genuinely strong; the implementation requires explicit design choices that the demo never raises.
What HRSD Is
ServiceNow’s HR Service Delivery is a case-based application for employee inquiries and lifecycle events — onboarding, offboarding, transfers, leave, separation, parental leave, accommodation requests. It complements rather than replaces the system of record for employee data (Workday, SuccessFactors, BambooHR). HRSD orchestrates the work; the system of record holds the authoritative employment data.
Case Management
HR cases live on hr_case (extending task) with their own categories, SLAs, and approval flows. Unlike IT incidents, HR cases routinely contain sensitive data — medical, legal, compensation, performance — and role-based access control is non-negotiable. Default IT-style assignment groups are not safe to reuse for HR cases without adding field-level ACLs that prevent over-broad visibility.
HR case category examples:
Benefits inquiry (low sensitivity)
Compensation question (high sensitivity, restricted)
Leave of absence (medium sensitivity, time-bound)
Workplace investigation (highest sensitivity, restricted to ER)Lifecycle Events
Onboarding, offboarding, and internal transfers are multi-step workflows touching IT (account provisioning, equipment), facilities (badges, seating), finance (payroll, expenses), and HR (paperwork, training). The Lifecycle Event Builder lets you orchestrate all parties without writing code, with parent-child task relationships that maintain the audit chain. Treating lifecycle events as glorified incidents loses the parent-child semantics and makes reporting on completion meaningless.
Employee Service Center
The employee-facing portal — catalog items, knowledge articles, case submission — branded to your organization. Keep it separate from the IT service portal to avoid confusion. Employees should land on the HR portal when navigating from an HR notification or an HR-themed link, not on the IT portal with HR articles bolted in. Service Portal supports multiple portal definitions; use them.
Data Privacy
HR data is regulated under GDPR, CCPA, HIPAA where applicable, and a long tail of local privacy laws. Configure ACLs per case type with field-level granularity, keep sensitive fields encrypted at rest using ServiceNow Vault or platform encryption, and audit every read of restricted fields, not just writes. HR data mistakes go to legal; the cost of a leak dwarfs the cost of designing properly the first time.
// ACL on hr_case.compensation_details (read)
// Restricted to HR business partners and the case subject
gs.hasRole('hrsd.hr_business_partner') ||
current.opened_for == gs.getUserID()Common Failure Modes
Onboarding cases routed through the IT incident assignment pattern — IT support sees compensation in the case context. Fix by separating HR case routing from IT incident routing entirely. Notification templates copied from IT that include sensitive fields in the email body — sensitive data leaves the platform via SMTP. Use minimal notification bodies that link back to the case, not data-rich emails. Lifecycle events configured as monolithic workflows rather than orchestrations of child tasks — when one child task delays, the parent does not surface the dependency.
What Changed in 2026
The Zurich release added Now Assist surfaces specific to HRSD — case summarization, suggested resolution, and policy article recommendations. The data-handling guarantees are the same as the rest of Now Assist; configure BYO LLM if regulatory requirements demand specific residency. Multi-turn Virtual Agent for HR topics (PTO requests, benefits questions) is licensed separately from ITSM Virtual Agent.
Implementation Sequence
Stand up the HRSD scope cleanly first — own portal, own knowledge base, own SLA framework, own assignment groups. Validate access controls with deliberate negative tests before any real data lands. Pilot with one HR business partner team on one case category for 30 days. Expand to additional categories and teams in priority order. Big-bang HRSD rollouts produce the most expensive errors precisely because the data is the most sensitive.
What to do this week: walk through the employee portal and the case form as a low-privilege user; every field that should not be visible but is, is a finding for your security backlog.
