Confidential HR Onboarding Across Five Departments
A 2,200-employee manufacturer runs ITSM Pro, CSM Pro, and HRSD in one instance. HR wants a single “New Hire” request in the employee portal. The process spans 45 tasks across HR, IT, facilities, payroll, and security. HR insists that salary, medical accommodation, and background-check status must never be visible to IT or facilities agents. The 300 contractors also need onboarding but must not see employee HR cases. The company has 18 catalog items, six flows, and a service portal, but no universal request configuration today. HR tracks onboarding in spreadsheets, causing a 9-day average delay and 22% incomplete first-day setup. The CIO wants one request number for each new hire and one dashboard. HR and IT have separate SLAs and separate reporting lines.
1. Where should the new-hire request be anchored: an HR case, a catalog item, or a universal request? Recommend the design and explain how it keeps HR data confidential.
Read the worked answer
Use a universal request as the umbrella, with an HR case for the confidential HR work and catalog tasks or requests for the other departments.
- The employee-facing entry point can be a catalog item in the portal. It captures only non-sensitive intake data: name, start date, role, location, manager, and equipment needs.
- The universal request gives one request number and a cross-department dashboard without copying HR data into every child task.
- The HR case holds salary, medical accommodation, and background-check status. Restrict those fields with HR roles and ACLs; do not put them in catalog variables, task short descriptions, notifications, or the universal request header.
- IT, facilities, payroll, and security get their own tasks or requests with only the data they need: start date, location, equipment profile, access role.
- Contractors: use separate user criteria and ACLs so they cannot see employee HR cases; if contractor data must be isolated administratively, evaluate domain separation, but do not assume it is required. This gives the CIO one number and one dashboard while preserving need-to-know.
2. How would you design the flow and SLAs so the 45 tasks do not become a 45-step bottleneck?
Read the worked answer
Do not model 45 sequential tasks. Use Flow Designer with parallel subflows and stage gates.
- Split into subflows by department: HR documents, IT account and device, facilities badge and desk, payroll, security clearance.
- Run independent tasks in parallel and use wait conditions for dependencies, such as device shipping waiting for start date and location.
- Put an SLA on each task and on the overall onboarding stage, not only on the universal request.
- Use decision tables for location, role, and contractor versus employee variations to avoid 45 branches.
- Assign a single owner per task and an escalation path; dashboard stage aging, not just closure.
- Keep sensitive HR approvals inside the HR case; expose only status such as “HR clearance complete” to the universal request.
- Measure first-day completeness, task cycle time, and handoff delay against the 9-day and 22% baselines.
3. What data-governance controls would you add for the confidential attributes?
Read the worked answer
Classify the data first: salary, medical accommodation, and background-check status are restricted; start date, location, and manager are internal.
Controls:
- Field-level ACLs and role separation in HRSD; use confidential HR profile fields where appropriate.
- Minimize propagation: no sensitive fields in universal request headers, task descriptions, notifications, or reports.
- Audit access and export; restrict list views and reporting on HR tables.
- Encrypt or restrict attachments that contain medical or background-check documents.
- Define retention and deletion rules.
- Test with a contractor and an IT agent to confirm they cannot see HR case data through related lists, search, or the portal.
- Add a data owner for each sensitive field and a periodic access review. Governance is not a one-time ACL; it needs testing and review.