HR teams that already run Salesforce can use it for the service side of people operations: employee questions, HR cases, onboarding and offboarding tasks, and a policy knowledge base. The HRIS stays the system of record for employees, pay and benefits. Salesforce reads a small, synced slice of that data and adds strict access controls for sensitive cases. Start with a few request types before adding AI.
What should HR run in Salesforce, and what should stay in the HRIS?
Keep employee master data, payroll, benefits enrollment and performance records in the HRIS. Use Salesforce for the work around those records: requests, cases, approvals, tasks and answers.
The HRIS is built for effective-dated job history, compensation and compliance filings. Salesforce is built for queues, routing, service levels and multi-team workflows. Trying to make either system do the other's job usually ends with duplicated records and two versions of the truth.
- Good fits for Salesforce: policy questions, letter and verification requests, leave inquiries, access and equipment requests, employee relations intake, and onboarding checklists.
- Keep in the HRIS: hire and termination transactions, salary, tax, benefits elections, and the official job and manager record.
- Gray areas: leave cases and address changes. The request can live in Salesforce while the HRIS still records the final change.
Which Salesforce products are built for employee service?
Salesforce sells an HR Service offering built on Service Cloud, with an employee portal, an HR agent console and Agentforce agents. Names and bundles have changed several times, so treat the labels below as a snapshot.
Salesforce's 2025 announcement described Agentforce HR Service, with an Employee Portal and an HR Service Console. Its current product page uses the name HR Service and lists an HR Service Desk, prebuilt service catalog items and HRIS connectors. Older Help articles still refer to HR Service Center and Employee Concierge, inherited from the Work.com era.
At Dreamforce 2026, Salesforce also previewed a combined IT and HR employee agent and resolution-based pricing for it. Those announcements did not state availability dates in the material we reviewed. Edition, license and agent-usage terms shift between releases. Ask your Salesforce account team what your contract includes before scoping.
You do not need the packaged product to start. Plenty of HR teams build on standard Service Cloud cases, queues and Knowledge. The packaged route adds employee-specific objects, a ready portal and HR connectors, which can save build effort if the licensing works for you.
How should HR cases be set up in Service Cloud?
Create a dedicated HR case record type with its own categories, queues and assignment rules. Keep HR cases out of customer-support views, reports and routing from day one.
A short category list works better than a long one. Most HR teams can start with eight to twelve request types, then add subtypes once real volume shows where the confusion sits. Each type should map to one owning queue, such as benefits, payroll questions, leave, HR operations or employee relations.
Decide early whether employees open cases through a portal, email, Slack or a chat agent. Every channel should land in the same case object so volume and resolution time are measured once. Salesforce Help also recommends splitting employees who work HR cases into two users: one as an employee, one as an agent. That keeps agents from seeing their own submitted cases in the console.
How do we keep sensitive employee data private?
Set the case object to private, then grant HR queues access through criteria-based sharing on the HR record type. Employee relations, investigations and medical cases need a further restricted tier.
The general mechanics are covered in our sharing model guide. For HR, the specifics are what matter. Your support managers should not inherit HR cases through the role hierarchy, so check where HR users sit in it. Restriction rules don't apply to cases, so use a separate record type, queue and public group for sensitive case types.
- Use a separate record type and queue for employee relations, with a small named public group.
- Hide sensitive fields with field-level security, not just page layouts.
- Turn on field history tracking for status, owner and category so changes leave a trail.
- Review who holds View All Data or Modify All Data. Those permissions bypass every HR sharing rule.
- If contracts or regulation require encryption at rest or detailed access logs, assess Shield Platform Encryption and Event Monitoring.
Where should employees find answers before filing a case?
Publish HR policies as Knowledge articles and surface them where employees already work: a portal, Slack or the intranet. Self-service only works when answers are short, current and easy to search.
Write articles around questions employees actually ask, taken from closed cases. Separate internal-only HR procedures from employee-facing articles using data categories or record types. Give every policy article an owner in HR and a review date, because benefits and leave rules change each plan year.
An Experience Cloud site can serve as the employee portal, with single sign-on so staff never need another password. The packaged Employee Portal plays this role in HR Service. If your company lives in Slack, Salesforce supports Slack-based employee help, though the exact app and license depend on your bundle.
How can onboarding and offboarding run across HR, IT and facilities?
Model each hire or departure as one parent record with child tasks for every team involved. Automation creates the tasks, and each team works its own queue.
A new-hire record can come from an HRIS event or from HR directly. It then generates tasks for IT accounts, equipment, badge access, payroll setup and manager preparation. Flow handles simple task creation. Flow Orchestration suits multi-stage processes where one team's step must finish before the next begins. Check your org's Orchestration run allowance with your account team before relying on it.
Offboarding deserves equal care, because a missed access removal is a security problem. Tie offboarding tasks to the termination date, and make account deprovisioning a tracked step with an owner rather than an email.
Which HR requests belong where?
The table below is a starting map. Adjust sensitivity and automation to your own policies and legal advice.
| HR request type | Where it lives | Data sensitivity | Automation |
|---|---|---|---|
| Policy and benefits questions | Knowledge articles, then a general HR case if unanswered | Low | Self-service search or AI answers grounded in policy articles |
| Employment verification and letters | HR case; letter produced from HRIS data | Medium | Template-based document generation with HR review |
| Leave inquiries and requests | HR case; leave balance and approval stay in the HRIS or leave system | High where medical details appear | Routing to the leave queue; restricted fields for medical notes |
| Personal detail changes | Request in Salesforce; the change is written to the HRIS | Medium | Integration call or task for HR operations |
| Onboarding | Parent onboarding record with tasks across teams | Medium | Flow or Orchestration triggered by a new-hire event |
| Offboarding and access removal | Parent offboarding record with IT and facilities tasks | Medium to high | Tasks tied to the termination date; tracked deprovisioning step |
| Employee relations complaints | Restricted case record type and queue | Very high | Minimal; manual triage by a named specialist group |
How should Salesforce connect to the HRIS?
Sync only the employee fields that service work needs, in one direction, from the HRIS into Salesforce. Write-backs should be rare, specific and logged.
A typical set is employee ID, name, work email, department, location, manager, start date, employment status and termination date. Leave compensation, government IDs and benefits elections out unless a defined case type truly needs them. Match records on the HRIS employee ID, never on email, since emails change with names.
The packaged HR Service includes connectors for several HRIS platforms, and middleware or a lighter integration tool works too. Whatever you choose, agree who owns failed syncs, because a missed termination update leaves a former employee with portal access.
Can AI answer employee questions safely?
Yes, for policy questions with clear written answers, if the agent is grounded only in approved HR articles. Anything involving judgment, medical details or conflict should go to a person.
Salesforce's own HR Service announcement described agents that escalate sensitive topics, such as bereavement, to human HR staff. Build that same rule into your own design, whatever tool you use. List the topics the agent must hand off, and test them before launch.
Actions that change data, like updating an address or banking details, raise the stakes. Start with read-only answers, add one or two low-risk actions after a pilot, and keep a human approval step for payroll-related changes. Agree ownership, review and audit with legal and security first; our AI governance guide covers that conversation.
What should HR report on without exposing individuals?
Report on volume, speed and deflection by request type and team. Keep named-employee detail inside HR and out of shared dashboards.
- Case volume by request type over time, to see which policies cause confusion.
- Median time to first response and to resolution, by queue.
- Share of questions answered by articles or an agent without a case being opened.
- Reopened cases, which often point to an unclear policy or a weak article.
- Onboarding tasks completed before the start date, by team.
Build these reports in a restricted folder, and summarize sensitive categories rather than listing them. For small groups, a count of employee relations cases by department can identify people. Roll those figures up or suppress them.
When is a dedicated HR service tool a better fit?
A standalone HR service desk or the HR module of your HCM suite may suit you better if Salesforce is not already central. Salesforce makes sense mainly when it is already licensed, administered and trusted.
Consider a dedicated tool when HR is the only Salesforce use case being proposed, or when no one will own the HR configuration after launch. The same applies if your HCM suite already includes a capable case module employees use. Conversely, Salesforce fits well when IT, facilities and HR want one shared request process.
What does a sensible first phase look like?
Pick a narrow slice, secure it properly, and measure it. Expand only once employees and HR staff trust the process.
- Agree the HRIS boundary and the short list of synced employee fields.
- Define eight to twelve HR request types with an owning queue for each.
- Build the private sharing model and restricted employee relations tier, then test it as real users.
- Publish the twenty or so policy articles behind the most frequent questions.
- Launch one intake channel, such as the portal or Slack, to one pilot group.
- Add onboarding tasks for one team pair, typically HR and IT.
- Review volume, resolution time and access logs before adding AI or new channels.
