# Update an employee's details

> Update an employee's details: 0 companies fully do it, 8 with a limit, 12 carry the tag. Every listing in HR & employee operations with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/hr.update-record/
- Markdown: https://www.anchorterminal.com/niches/hr.update-record/index.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/niches/hr.update-record/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/hr.update-record/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 8 | 12 | 7 | 0 |

## What counts as done

The field changed with the effective date, the change attributed to the agent's token in the audit log, and sensitive fields (pay, bank) refused unless the user may edit them, in one call.

How agents ask for it: change my address; update Kim's job title; record the pay rise from April; fix the start date

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **BambooHR (Bamboo HR LLC)**: POST /employees/{id} updates fields, and table rows (job, compensation) carry effective dates through the table endpoints. Whether the audit log names the token or app for API edits was not found.
- **Deel (Deel, Inc.)**: PATCH /people/{id}/personal and the address and department endpoints change one area per call with an Idempotency-Key. No effective date on these writes or audit log naming the token was found.
- **Factorial (Everyday Software, S.L.)**: Updates an Employee changes profile fields and compensation records carry their own dates; whether the audit log names the token for API edits was not found, and an API key grants every scope.
- **HiBob (Hi Bob Ltd.)**: PUT /people/{identifier} updates specific fields under field-level permissions, so blocked fields are refused for the service user. Effective dating of table entries and the audit actor for API edits were not read.
- **Humaans (Humaans Software UK Ltd)**: PATCH /api/people/:id updates profile fields and compensations carry an effectiveDate, with compensation writes needing their own compensations:write scope. No audit log naming the token was found in the reference.
- **Remote (Remote Europe Holding B.V.)**: PATCH /v2/employments/{id} and the personal, address and bank detail endpoints update one area per call, with contract changes tracked as pending changes. No audit log naming the token was found, and no idempotency key exists.
- **Rippling (People Center, Inc. dba Rippling)**: Worker changes record effective_on and applied_on, but no write endpoint for an existing worker's fields is in the v2 reference list read, so updates go through the product or draft flows.
- **Zoho People (Zoho Corporation Private Limited)**: Form records can be updated with inputData by label name, one call. No effective-date parameter for employee field changes or audit log naming the token was found in the pages read.

## What stops agents finishing

- edits to pay need a second approver the agent cannot be

## Around it

Before: hr.directory-lookup. After: hr.sync-people.

## Where this comes from

Weight 7 of 100 in HR & employee operations: no first-hand account; vendor docs only (Deel personal information, Humaans job roles and compensation); smallest share

As data: https://www.anchorterminal.com/api/v1/use-cases/hr.update-record.json, or the MCP tool get_use_case with id hr.update-record. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
