Audit Log
Use the audit log to investigate recorded activity, and Data Export to obtain a downloadable set of company records. They serve different purposes: an activity log is not a backup, and an export is not a history of every change.
Open Audit Log (/audit) with view_audit_log to inspect activity in your current company. Rows show the time, action, entity, actor, description and IP address. Filter by entity and date, or search the loaded rows. The Export CSV button requires export_reports and exports the filtered rows the page has loaded, up to 250.
The log covers authenticated changes that reach the application's activity logger, including failed actions, and selected report downloads. Requests blocked before an action starts may not appear. Background work and AI tool activity do not necessarily produce separate rows here, so absence of a row does not prove that no activity occurred.
An action can finish before its audit record is written. Open an entry to see its details; previous and new values appear when supplied, but are not available for every changed field.
The Start date and End date filters include the whole of each day you pick, counted in UTC. To see one day, pick the same date in both.
Employee profiles, leave requests and pay runs also have an activity timeline. It merges audit events for that record with notes you can add. You need the view permission for that record to see it.
Investigate an action
- Check that you have selected the correct company.
- Narrow the date range and entity, then inspect the actor, action and description.
- Open the relevant entry and compare it with the record in its application page.
- If you need a copy, export the filtered loaded rows as CSV. This exports what the page has loaded, not every matching event in the system.
Support activity
Platform staff accessing a company they do not belong to appear as Arche Support. A recorded support session supplies a reason. Selected support reads are logged as well as writes; notification, health and current-profile reads are excluded. Support sessions are an accountability record, not a prerequisite enforced by the access guards. When one starts, people with manage_company get an alert. See Security Overview.
Platform administrators choose the company from the top bar. Platform-wide activity also has a separate platform audit API; it is not all stored against an affected tenant.
Data Export
The Data Export page (/data-export) requires export_reports and manage_users, plus the Data Export module licence. The REST controller requires export_reports and that licence; the additional manage_users check is in the page, so it is not a second API permission requirement.
Click New Export, choose a type and format, then Request Export:
| Type | Included records |
|---|---|
personal_data | Selected employee identity and employment fields |
payroll | Pay-run history |
performance | Review records |
compliance | Compliance document metadata |
full_export | The four sections above, shown as Summary export. It leaves out sections your company is not licensed for |
company_archive | Shown as Complete company archive (ZIP): one file per table that holds records, plus a files folder with every uploaded file. Credential columns (password hashes, tokens, API keys, webhook headers) and a few internal tables are left out. It needs manage_company and payroll read, and supports CSV or JSON only |
custom | Your selection of employees, payroll, performance and compliance sections |
The types you are offered depend on your permissions. payroll needs payroll read (view_payroll or manage_payroll) and view_all_payroll. compliance needs view_all_documents. The archive needs manage_company. Sections for modules your company is not licensed for are hidden.
You see the exports you requested. People with manage_company see everyone's. An export contains only what the person who requested it could see when it ran.
Choose CSV, JSON or XLSX. Custom exports require at least one section. XLSX uses a worksheet per section. CSV protects formula-like values; XLSX writes strings as text. JSON preserves the exported values.
An export is a defined set of records, not a complete database backup or a guarantee that every item needed for a subject access request is included. Document contents and all other modules are not implied by full_export.
Employee scope
The API accepts employeeId and narrows the included sections to that employee, using individual pay-run items for payroll. The current New Export form has no employee selector and requests company-wide exports. An authorised API client is needed for employee-scoped requests.
Processing, cancellation and download
Requests move from pending to processing, then completed or failed. Wait for completion before downloading. If a request remains pending or fails, check its status message and contact your administrator with the request details.
Pending or processing requests can be cancelled. Cancellation is stored as failed with a cancellation message, not a separate cancelled status. A file produced after cancellation is discarded.
Download completed exports using the row's download button. Downloads expire seven days after completion; cleanup subsequently removes the stored file and marks the row expired. Request a fresh export when needed. Store downloaded personal information only where your company's data-handling policy allows it.
Creating and cancelling exports reach the audit interceptor. Ordinary tenant downloads at /data-export/:id/download are not separately captured by its report-download rule; platform-support read logging can still apply.