Skip to content

Vault Search & Filtering

The Provenance Vault logs every anonymization request your workspace processes. Search and filter lets you quickly locate specific records for compliance audits, incident investigations, and data governance reviews without scrolling through the full log.

Available filters

Filter What it does
Status Show only success, error, or blocked records
Entity type Show only records where a specific entity type was detected and stripped (Person, Email, Phone, Organisation, SSN, Credit Card, Signature)
Model Filter by the model identifier used, partial match supported (e.g. gpt-4o, browser-extension)
From date Show records created on or after this date
To date Show records created on or before this date

All filters are combined with AND logic. A record must match every active filter to appear in results.

Using the filter bar

The filter bar sits above the vault table in the Vault tab of your Redact workspace.

Status dropdown, select a status to narrow results to successful requests, errors, or blocked requests only.

Entity type dropdown, select an entity type to show only records where that type was detected. For example, selecting Email returns every request where at least one email address was stripped. Useful for answering questions like "which requests touched personal names?" or "how many requests contained credit card numbers?".

Model field, type any part of the model name. The filter applies after a short pause as you type. Use this to isolate browser extension activity (browser-extension), a specific LLM (claude-opus-4), or document uploads (browser-extension-doc).

From and To date pickers, set a date range to scope the audit window. Useful when preparing evidence for a specific period, such as a quarterly compliance review or an incident window.

Clear button, appears automatically when any filter is active. Click it to reset all filters and return to the full log.

Record count, displayed next to the clear button showing how many records match the current filters.

API

The vault list endpoint accepts the same filters programmatically, useful for building custom audit pipelines or exporting filtered results.

GET /api/redact/{workspace_id}/vault

Query parameters

Parameter Type Description
status string success, error, or blocked
entity_type string Entity type key: PERSON, EMAIL, PHONE, ORG, SSN, CREDITCARD, SIGNATURE
model string Partial match on model_used field
from string ISO date, e.g. 2026-05-01
to string ISO date, e.g. 2026-05-31
page integer Page number, default 1
per_page integer Results per page, max 100, default 25

Example, all requests that stripped a person name

GET /api/redact/{workspace_id}/vault?entity_type=PERSON

Example, email detections in a specific month

GET /api/redact/{workspace_id}/vault?entity_type=EMAIL&from=2026-05-01&to=2026-05-31

Example, filter by date range and model

GET /api/redact/{workspace_id}/vault?from=2026-05-01&to=2026-05-31&model=gpt-4o

Example, show only blocked requests

GET /api/redact/{workspace_id}/vault?status=blocked

Response

{
  "ok": true,
  "records": [...],
  "total": 42,
  "page": 1,
  "per_page": 25,
  "pages": 2
}

Common audit queries

All requests that touched personal names

Select Person from the Entity type dropdown. Returns every record where at least one PERSON entity was detected, regardless of how many.

All requests in a specific month

Set From to the first of the month and To to the last day. The total record count gives you the full activity for that period.

Credit card detections across all time

Select Credit Card from the Entity type dropdown with no date range set. Use this to verify that financial data is being caught and to estimate exposure scope.

Browser extension activity only

Type browser-extension in the Model field. This covers both text anonymization (browser-extension) and document uploads (browser-extension-doc).

Failed or blocked requests

Select error or blocked from the Status dropdown. These records include a blocked_reason field explaining why the request was rejected.

Requests in a specific incident window

Combine From and To with a narrow date range to isolate exactly what was processed during an incident. Export the filtered view as a PDF from the Export PDF button for your incident report.