Customer work, connected.

Help & supportMyAccount
Employee Record Approvals · How-to guide

Submit a controlled employee amendment

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to send a sensitive v1.3.0 employee change to the Approval Queue with encrypted payload, changed-field list and reason.

Audience: HR administrators and authorised managersPermission: Human Resource Management: ViewModule v1.3.0
Jump to steps
Where to go Admin Area → Human Resources → Employee Record Centre → Select employee → Current Record
Code-backed scope These instructions follow Human Resource Management v1.3.0. Use only controls visible to your permission level and confirm the saved record or audit entry after every action.

Before you start

  • Access to Admin Area → Human Resources → Employee Record Centre → Select employee → Current Record.
  • The Human Resource Management: View capability or administrator access.
  • The correct employee, record, period or authorised evidence.

Follow these steps

  1. Change one or more controlled/sensitive fields.
  2. Enter a clear amendment reason.
  3. Click Save & Synchronise.
  4. Verify the response states that approval is required.
  5. Go to Approval Queue and verify the request reference, changed field names and pending status.

Fields and options

Request referenceGenerated unique amendment reference.
Changed fieldsField names only in normal queue/notification views.
Before hashUsed to detect a record changed after the request was created.
Encrypted payloadProtected before/after values stored using the onboarding encryption service.

What the module checks

  • The action is permission-aware.
  • Required values must pass the exact server-side validation.
  • Verify the saved record and audit/log result.

What happens next

The module saves the permitted change and records the resulting status, version, delivery or synchronisation evidence. Reopen the relevant register and verify it.

Troubleshooting

  • If the control is missing, confirm the required HRM permission and module version 1.3.0.
  • If saving fails, correct the exact field or state named in the validation message.
  • If an email/automation is missing, review the module delivery/audit log and host cron/mail settings.
HR data safety Restrict identity, right-to-work, payroll, bank, health, disciplinary and document information to authorised staff. Do not place protected values in free-text notes, email recipients or screenshots.
Browse connected topics: employee record approvals

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page