AI agents for HR & people operations: How they work and where they fit

Much of the AI in HR today is a chatbot that answers policy questions inside one HR system. That covers vacation lookups but does little for headcount requests, compensation cycles, and attrition reviews, which still move across disconnected systems. To get that work done, 68% of surveyed U.S. HR professionals rely on workarounds like spreadsheets, shared drives, and manual tracking. AI agents for HR and people operations take over that cross-system work. They read governed people data across the human resources information system (HRIS), applicant tracking system (ATS), payroll, and survey tools. Then they act on it, with a human approving the changes that matter.

What are AI agents for HR & people operations?

AI agents for HR and people operations are AI systems that read people data, reason through multistep HR workflows, and take scoped actions. They work under the permissions and approvals HR already uses. Typical actions include drafting a requisition, routing a comp change for sign-off, updating a record, and notifying a manager.

The work starts with a person. Someone sets the goal and configures what the agent can see and do. The agent carries that goal across the steps, and it runs on its own only where someone configured it to.

AI agents vs. HR chatbots

A basic chatbot answers a question and waits for the next prompt. Ask it about parental leave, and it returns the policy. An agent handles the process around the question. Given a promotion request, it checks the new pay against the salary band, drafts the change, and routes it to the comp partner.

Many vendors now relabel assistants as agents, a practice called "agentwashing." Both can sit behind a chat window, so judge a system by the actions it can take. Check whether it can carry a multistep workflow across the data and systems your process touches.

How AI agents use rules-based HR automation

Rules-based automation, including robotic process automation (RPA), follows a fixed path. It handles structured, repetitive steps well, such as setting up payroll for a new hire. On its own, it hits limits when a request falls outside its rules, like a requisition with a new job code or a missing cost center.

An agent can run those rules as steps inside a larger workflow. Builders assign fixed, rules-based actions to steps that must come out the same way every time, and the agent handles the context and lookups around them. Given a requisition with a missing cost center, it can look up the hiring manager’s department, propose the right code, and send the request through the standard approval rules. Most HR processes mix both kinds of steps, and one agent can carry both.

Where HR systems and spreadsheets hit limits

People data sits in several systems, so HR teams answer cross-system questions through exports. AI assistants built into any one of those systems inherit the same boundaries.

People data split across HRIS, ATS, payroll, and survey tools

Finding which teams are over headcount budget and losing strong performers takes data from four places. You need headcount from the HRIS, the plan from finance, performance ratings, and open requisitions from the ATS. Pulling from several systems is typical, and 91% of HR survey respondents need two or more systems to finish a single HR task. Different employee ID fields in the ATS and payroll often make the data hard to join.

Spreadsheet handoffs for compensation and headcount

Headcount plans often live in static spreadsheets that drift from the HRIS as people join and leave. A requisition moves from manager to finance to HR as separate email forwards. Comp cycles run the same way. Managers edit individual spreadsheets, and someone has to merge them by hand.

Assistants scoped to a single HR system

HRIS vendors now ship assistants and agents inside their platforms, and those tools work well on that platform's data. But the average large company runs about 400 apps, and more than 100 of them touch employees. An assistant inside the HRIS can't see the engagement survey, the finance plan, or the ATS pipeline unless someone builds and maintains that connection.

Use cases for AI agents in HR & people operations

The strongest early use cases share a pattern. The work recurs at high volume, pulls data from several systems, and ends in a decision someone has to approve.

Headcount planning and hiring requests

A hiring manager submits a request with role, level, department, start date, and target compensation. The agent checks the request against the approved plan and current budget, flags deviations, and drafts the requisition. It routes standard requests to the usual approvers and sends over-plan requests for additional sign-off. Finance and HR then approve one shared record instead of trading email threads.

Attrition and retention risk

Attrition models draw on promotion history, tenure, engagement, performance, and overtime. Each week, an agent can watch those signals, flag teams where risk is rising, and draft a summary for the HR business partner. The agent surfaces the risk, and the manager decides what conversation to have.

Compensation review cycles

Comp review cycles combine market data, performance ratings, budget, and pay equity checks. An agent can pull employee data, apply merit guidelines, and flag employees paid well above or below predicted pay. It then drafts recommendations that show the cost. Each recommendation goes to a manager and a comp partner for approval. Most organizations have automated only pieces of this work, with 70% reporting some compensation automation and only 1% saying they've reached an advanced stage.

Employee survey analysis

A company-wide engagement survey can produce tens of thousands of open-text comments. Given those comments, an agent can classify them by theme and sentiment and compare the themes across teams. It uses those comparisons to draft manager-level summaries. Where survey confidentiality commitments allow, the agent can also compare aggregated themes with attrition records. Managers can then see which concerns line up with actual departures.

Onboarding and offboarding coordination

Onboarding touches HR, IT, payroll, facilities, and the hiring manager. For each accepted offer, the agent can open provisioning requests by role and location and confirm each step finished. Offboarding carries security risk as well, and 79% of former employees say at least one work account or access point kept working after their last day. Matching HRIS terminations against access lists lets an agent route deprovisioning requests the day someone leaves.

What AI agents need to work safely with people data

People data includes compensation, performance ratings, and personal details. An HR agent is only as useful as the controls around it.

Permission-scoped access to employee data

Access for an agent should match what the person using it may see. In a shared channel, an executive's agent can expose executive compensation to junior analysts. Scope access before retrieval so restricted rows never reach the agent. Row-level security does this at the data layer, and column-level security hides sensitive fields such as salary. A manager sees direct reports, a department head sees the department, and the chief human resources officer (CHRO) sees the whole company.

Human approval on employee-affecting changes

Changes that affect employees, such as pay changes, status updates, and new requisitions, need a human sign-off. Approval on every action doesn't scale, so lookups and drafts can run without it. The EU AI Act sets a similar expectation. It treats certain AI uses in recruitment and worker management as high-risk. Human oversight and logging obligations for those systems apply from December 2, 2027.

An audit trail for every agent action

Each agent action should leave a record of who asked, what data the agent read, what it proposed, who approved, and what changed. HR, legal, and auditors need that record to explain a decision months later. A log that captures only the final write can't show why the agent proposed it.

A single governed source of people data

Finance, HR, and operations often run three different definitions of headcount. Exported copies hand all three to the agent. A cloud data warehouse such as Databricks, Snowflake, BigQuery, or Amazon Redshift can hold all of that people data under one governance model. Teams still have to agree on one headcount definition and configure who sees what. The agent then reads the same governed tables the people analytics team already trusts.

How Sigma supports AI agents for HR & people operations

Those four controls hold best when the agent runs where the people data already lives. Sigma is the AI apps and analytics platform that lets users build agentic analyses and applications directly on live cloud data warehouse data. For HR, that means agents work on governed people data under the same rules as the rest of the business. IT controls data access, and people operations uses agents to carry out HR workflows.

Sigma agents with inherited permissions and row-level security

Sigma agents inherit the running user's Sigma permissions and workbook-level grants. On OAuth connections, queries also run under each user's warehouse role, so warehouse row-level security applies. A builder then scopes which tables and columns each agent can read and which tables it can write to. If row-level security limits a director to her org, an attrition agent answers her questions from those rows only.

Agents run on the AI provider the customer picks, either an external provider or a warehouse-hosted model in Databricks, Snowflake, or BigQuery. With a warehouse-hosted model, the customer's data platform manages the data end to end.

Human-in-the-loop approvals before an agent acts

Sigma agents support human-in-the-loop approvals in chat. For actions a builder configures to require approval, the agent proposes, and the user approves before the agent writes or sends anything. In the hiring-request workflow, the agent drafts the requisition and waits. Once the manager approves, it updates the status and emails the finance approver. Scheduled runs skip approval prompts, so route employee-affecting actions through chat or a separate approval step.

Builders configure each agent within a workbook context. They can also give an agent action tools, which run predefined workbook actions the same way every time. Rules-based steps, such as a status update or a notification to the finance approver, stay deterministic while the agent reasons through the rest. The same agent can run as a chat element in an AI app, and AI assistants or scripts can call it through the Sigma MCP Server or Sigma REST API.

Write-back through input tables for headcount and comp changes

Input tables write headcount plan changes and comp recommendations back to the warehouse from the workbook. Each change lands in an audit trail that records the original record, the new record, who changed it, and when.

In Sigma AI apps, teams enter and review these changes in one workspace. For a comp cycle, the comp partner reviews and approves recommendations alongside the underlying numbers. The same input tables and actions run in the more than 8,000 AI apps Sigma customers have built. Duolingo's people analytics team used input tables to replace manual processes and uses row-level security to set granular access to sensitive data.

Build AI agents for HR & people operations with Sigma

Start with one recurring people operations workflow, such as hiring requests or a comp cycle. Then ask three questions about the agent you'd adopt:

• Can it see the right data, and only the data its user can already access?
• Does it ask for approval before it changes anything that affects an employee?
• Does it leave a record of what it read, what it proposed, and who approved?

Roll an agent out to a second workflow only after it passes all three on the first.

Sigma runs HR agents on governed warehouse data, under the permissions HR teams already use, and logs every change teams write back. Get a demo to see an HR agent work on your own people data.