Appearance
File Review & Batch Redaction
File Review gives teams a controlled path from uploaded or ingested files to approved release or rejection, with optional batch redaction and threat reanalysis when policies require another look.
Review queue
Files that need human judgment land in a review queue while in a pending state. Reviewers see items awaiting decision so nothing approved for wider use slips through without inspection.
Typical queue properties include file identity, submission time, priority, and linkage to policies or matters (where configured).
Approve / reject workflow
Reviewers can:
- Approve — Accept the file for its intended use (for example, sharing with a model or storing in a governed library).
- Reject — Block or quarantine with a reason so senders or admins can correct issues.
This workflow keeps a clear audit trail: who decided what, and when.
Batch redaction
For large or repetitive workloads, batch redaction applies redaction rules across many files or regions at once—consistent with your PII and policy configuration—so teams do not redact files one-by-one when a batch operation is appropriate.
Threat reanalysis
When content or context changes—or when policy requires it—reviewers can trigger threat reanalysis so files are rescanned or re-evaluated under current threat and PII rules before approval.
Authentication
File review APIs and UI actions run in the context of the signed-in tenant via TenantContext: requests are scoped to the tenant, and users only see queues and actions permitted for their role within that tenant.