Approving a Profile Change
The HR queue where an employee's proposed contact, emergency and bank changes are read as a diff and confirmed — or sent back.
Nothing an employee types about themselves lands on their record directly. Every edit they make in My details becomes a change request, and this is the queue where it is confirmed.
/people/change-requests, reached from Needs you on the People overview whenever something is waiting.
Reading a request
Each request is one card:
| On the card | What it tells you |
|---|---|
| Name and employee number | Who is asking, and their department. |
| Status | Awaiting confirmation, Approved, Rejected, or Cancelled. |
| Note from the employee | Optional context they wrote when submitting. "Changed banks in August" saves a phone call. |
| The diff | One row per field, as old value → new value. Only fields they actually changed appear. |
| Submitted date | And, once decided, the date it was decided. |
Account numbers are displayed in full on this queue. HR has to be able to check what is about to land on the record against whatever evidence the employee provided — a masked number cannot be verified, and an unverified bank change is how salary ends up in the wrong account.
What can be proposed
Only these fields. Anything else — name, email, job title, pay — is HR's to change on the record.
| Group | Fields |
|---|---|
| Contact | Phone, address. |
| Emergency contact | Name, relation, phone, alternate phone, email, address. |
| Bank | Bank, bank branch, account name, account number, sort code, SWIFT code. |
The labels on this queue and the labels on the employee's own page come from one place, so a field is never named two different ways on the two sides of the same request.
Deciding
Pending is the working set — everything still waiting on you. Decided is the record of what was approved or rejected, and when.
A bank change is usually three fields at once. Check every row against whatever the employee sent you.
Approve confirms first, then applies every field to the employee record in one transaction — the record updates immediately. Reject leaves the record exactly as it was and lets you attach a note explaining why; the employee can submit again.
Approving takes no note — the diff is the record of what changed. The optional note is offered when you reject, because that is the decision the employee needs an explanation for.
Empty and unavailable states
| What you see | What it means |
|---|---|
| Nothing awaiting confirmation | The queue is clear. Switch to Decided to see history. |
| No decided requests yet | Nothing has been approved or rejected yet. |
| Self-service updates are not enabled yet | The feature detects its own storage. Where it has not been enabled for your business the page says so plainly rather than failing, and nothing is lost. |
Who can reach this page
| Role | Access |
|---|---|
| Personnel users | Yes — reading requires the Personnel feature, deciding requires write on it. |
| Staff (employees) | Never. It shows other people’s data, so Staff are sent to their own dashboard. |