Governance - reviews, approvals, audit

Proposed. Reviewed. On the record.

Foldr Governance routes changes and documents for sign-off before they land, right where your files already live. Multi-step approvals, reviewer pools per share, deadlines and escalation, and a tamper-evident audit trail of every request, step and decision. Reviews and approvals are part of Foldr Enterprise; classification-based routing is the Governance add-on.

Finance / Payables / 2026 In review
Invoice 10042 – Acme Ltd.pdf
Rule: amount > £10k Classified: Commercial Due in 2 days
Approval chain
  • 1 Line manager (any one) Approved Mon
  • 2 Finance reviewers (quorum of 2) 1 of 2
  • 3 Compliance (classification) Waiting
Requester can’t self-approve · every decision audited
Features

Sign-off built into your files, not bolted on beside them.

Governance runs on the same shares, permissions and custom fields as the rest of Foldr. The thing under review is the file itself, the reviewers come from the directory you already use, and the audit trail lives in the same activity log as everything else.

Routing rules that catch the right things

Match by trigger and priority: a document’s classification, a specific custom-field change, or any change on a share. The rule decides what needs sign-off and who it goes to, so the right items are held and everything else flows straight through.

Multi-step approvals

Build a chain of steps, each cleared by any one reviewer, by everyone, or by a quorum of N. A proposed field change is held until its reviewers sign off, and only then does it commit. Nothing lands half-approved.

Reviewer pools, split by job

Assign who approves field changes and who approves classification routing independently, granted globally or per share. Every reviewer is scoped to files they can already read, so review never widens access.

Deadlines and escalation

Due-in timers on every step, automatic hand-off to a fallback approver when a deadline passes, and a scheduled sweep that chases overdue requests. Approvals don’t quietly stall.

Actions when a decision lands

On approve or on reject, run a MaSH automation, send a notification, or move the file the moment the outcome is recorded. The decision is the start of the next step, not a dead end.

No self-approval, fully audited

A requester can never approve their own change. Every step records who decided, when and why, and the whole request carries a tamper-evident audit trail. Approvals waiting on you surface in Shared with me.

How it works

Catch it, route it, decide it, keep the record.

A change or a document is held the moment it matches a rule, routed to the right reviewers, and committed only when they sign off.

1 · Route

A rule catches the change

Author routing rules matched by trigger and priority: a classification, a specific custom-field change, or any change on a share. When something matches, it’s held for review instead of landing straight away, and sent to the reviewer pool you nominated.

2 · Review

Reviewers sign off, step by step

Each step clears by any one reviewer, by everyone, or by a quorum of N. Reviewers see only files they could already read, the requester can’t approve their own change, and approvals waiting on someone surface in their Shared with me.

3 · Decide

The outcome commits, and acts

On approval the change lands; on rejection it doesn’t. Either way, on-approve and on-reject actions can run a MaSH automation, notify, or move the file, and the whole decision is written to a tamper-evident audit trail.

+ Deadlines

Nothing stalls in a queue

Every step carries a due-in timer. Miss it and the request hands off to a fallback approver automatically, while a scheduled sweep chases everything overdue. The work moves whether or not someone’s watching the queue.

+ Classify

Classification can raise its own review

With the Governance add-on, detectors classify files as they’re indexed, by sensitivity or retention category. A classification can itself raise a review, routing a file that looks sensitive to a designated reviewer to confirm or reclassify, through the very same engine.

Reviews vs Governance

A baseline engine, and an add-on on top.

Reviews and approvals are part of Foldr Enterprise: routing rules, multi-step sign-off, deadlines, on-decision actions and the audit trail. Governance is the separate add-on that layers classification and policy over the same engine, detectors, sensitivity labelling and retention, and the classification-triggered reviews they raise. Because Governance routes through the review engine, it always includes Reviews; you never buy classification routing without the approvals underneath it.

Same permissions, same shares

Review never widens access.

Reviewer pools are assigned globally or per share, and split by job: who approves field changes and who approves classification routing are set independently. Whichever pool they’re in, a reviewer only ever sees a file they could already open. Sign-off adds a gate in front of a change; it never hands anyone a key they didn’t already hold.

With the rest of Foldr

Sign-off is a step in a workflow, not an island.

Because a review acts on a real file with real custom fields, the rest of Foldr is right there with it. Captur extracts the fields that a rule keys off. Search and Grace see the same documents and decisions. MaSH runs the moment an approval or rejection lands, routing, reconciling, or kicking off whatever comes next.

Curious whether Foldr would fit?

Try it free for 30 days, no credit card. Or get in touch about self-hosting.