Pixie CRMHelp Centre
Protected Exports & Report · How-to guide

Generate a protected HR export

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 create a CSV export job for an implemented HR report source.

Audience: HR administrators, authorised managers and payroll staffPermission: Human Resource Management: ExportModule v1.3.0
Plain textJump to steps
Where to go Admin Area → Human Resources → Reporting & Exports → Generate Protected Export
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 → Reporting & Exports → Generate Protected Export.
  • The Human Resource Management: Export capability or administrator access.
  • The correct employee, record, period or evidence reference before making a change.

Follow these steps

  1. Go to Admin Area → Human Resources → Reporting & Exports → Generate Protected Export.
  2. Select the exact employee, period, document, request, rule, queue item or record shown by the screen.
  3. Complete every required field and review the field descriptions below before submitting.
  4. Check the current status and any warning, duplicate, eligibility or permission message.
  5. Click Generate Protected Export once and wait for the success or validation response.
  6. Return to the register and confirm the new status, reference, audit event and any generated file or downstream record.

Fields and options

Report sourceChoose one of the implemented registers, queues or audit datasets.
Export formatThe protected reporting workspace currently generates CSV files.
Job status and hashUse the export history, row count and stored hash to identify the generated file.
Download or void actionDownloads are counted; voiding requires a reason and preserves the audit history.

What the module checks

  • Your assigned HRM capability must permit the action.
  • Required dates, amounts, references and reasons must pass server-side validation.
  • Approval, publishing, locking, voiding, withdrawal and deletion actions are allowed only from the states implemented by that workspace.
  • A success message is not a substitute for checking the register, audit log or generated file.

What happens next

The result remains available from Admin Area → Human Resources → Reporting & Exports → Generate Protected Export. Confirm its identifier, status, linked employee or period, dates and audit/activity record before relying on it operationally.

Troubleshooting

  • If the menu or action is missing, confirm the module is active and your HRM capability is assigned.
  • If validation fails, correct the exact field named in the message; do not bypass the rule in another workspace.
  • If a downstream email or automation does not run, check the related delivery/audit log and the host application cron or mail configuration.
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: protected exportsreport
Choose an HR report sourceReview HR reporting coverageDownload a protected HR exportVoid a protected HR export

Keep the workflow connected

Move from the product overview to a related capability, connection or practical guide.

Help Centre

Team access guides

Set up staff, departments and permissions.

Module

HR management

Explore the product overview for this area of work.

Integration

Microsoft 365 integration

Connect work with the tools your team already uses.

Practical guide

CRM implementation guide

Plan ownership, onboarding and a useful first rollout.