Home / User stories / Remediation guardrails
ROHana · Records Operations
Remediation guardrails

Act on millions of documents — without breaking anything.

Hana can find what’s wrong; acting on it at scale is what scares her. She needs to dispose, relabel, and dedupe across the estate behind permission, hold, approval, and audit guardrails.

The reality today

Bulk action is where things break

Irreversible mistakes

One bad bulk disposition can destroy records under hold.

No approvals

Destructive actions run without a human in the loop.

No proof

After a mass change, there’s no clean record of what happened.

How the system works

Preview first, approve, then act — all logged

Recommended actiondispose · relabel · dedupeGuardrailcheckexpired recordRequires approvalhuman in loopunder legal holdBlockedhold winssafe duplicatePreview → rundry-run first
See it in the product

Preview by default, approvals for destructive, holds block

Remediation

Act on the estate — behind guardrails

Recommended actions like dispose, relabel, and dedupe run preview-first. Destructive ones require approval, anything under legal hold is blocked outright, and you can dry-run the whole batch before committing. Every executed action writes a tamper-evident ledger entry with actor, approval, and timestamp.

Fileport product — Act on the estate — behind guardrails
What happens, step by step

From problem to proof

1

Preview everything

Recommended actions run preview-first — nothing executes by surprise.

2

Gate destructive actions

Disposals require approval; anything under legal hold is blocked outright.

3

Dry-run the batch

Test the whole batch before committing a single change.

4

Log every execution

Each action writes a ledger entry with actor, approval, and timestamp.

Why it lands

What lets Hana hit ‘run’

Preview
by default
Blocked
under legal hold
Logged
every executed action
FAQ

Common questions

Can a disposal hit a held document?

No. Held documents are blocked from disposition outright.

Do destructive actions need approval?

Yes, and you can dry-run the whole batch before committing.

Is each action recorded?

Every executed action writes a tamper-evident ledger entry.

Related reading

Keep exploring

See this on your own data.

Book a demo — we’ll connect a system, ingest a sample, and show this working on your estate.

Book a demo