Appearance

Audit log ​

Available onEnterprise
Who can do thisOwners and admins

The audit log is a record of what your team does: member invites and role changes, settings and branding updates, report views and downloads, exports and deletions. Hiring-manager decisions and link opens are in it too, under the hiring manager's email.

Entries are kept for 2 years.

Open the audit log ​

  1. In the sidebar, click Settings, then Audit log.

The table has three columns: When, What happened and Details. Times are shown in your time zone. Use ← Newer and Older → to page through.

Recruiters and viewers see The audit log is for company owners and admins.

Filter the log ​

  • Show picks a kind of activity: All activity, Team and invites, Security and sign-in, Invites, requests and decisions, Reports and exports, Settings, branding and deletions, Integrations, Sourcing and careers, Billing or Infyva support.
  • Person shows one teammate's actions, or Everyone.

Infyva support lists the times Infyva staff opened your workspace to help you.

Export the log ​

From the audit log page: click Export CSV. The export is in UTC.

The full log as CSV or JSON:

  1. Open Settings > Sign-in rules.
  2. Under Audit log export, click Download CSV or Download JSON.

Stream the log to your SIEM ​

You can have new audit events sent to your SIEM or any HTTPS collector.

  1. Open Settings > Compliance policies.
  2. Under Audit log to your SIEM, enter the Endpoint URL.
  3. Tick Also send events from before today if you want the history too.
  4. Click Start sending.
  5. Copy the signing secret into your collector. It is shown once.

New events are sent every 5 minutes as newline-delimited JSON, up to 500 per request. Each request is signed with HMAC-SHA256 in the X-Infyva-Signature header. If your endpoint is down, the same events are sent again on the next run, so nothing is skipped. De-duplicate on id.

The same section has Send a test event, Send now, Save URL, Stop sending and New secret. It shows how many events were sent and when the last one succeeded.

Pull the log with the API ​

You can also read the audit log with an API key that has the read:audit_log scope:

GET /api/v1/public/audit-log?after=<cursor>

Events come oldest first. Pass the X-Next-Cursor header from the last response as after to get only newer ones. See Public API.

When someone's data is erased ​

If a person's data is erased, their audit entries are kept, but their email is replaced with a pseudonym and their IP address and browser details are removed. See Export and erase data.

Next steps ​