Reviews sends a file to named approvers when something about it needs a decision. A rule says when that happens, who approves, how long they have and what Foldr does once they decide. This article is for the administrator who sets those rules up. The approvers’ side is in Approving requests in Foldr.
The request panels, pausing a request and deciding from the file viewer are on Foldr Cloud now and on appliances from 11.3.
What you need
- Reviews switched on for your Foldr. Reviews is part of the Enterprise plan on Foldr Cloud. If Reviews & approvals is missing from Foldr Settings, the feature is not licensed yet.
- Permission to set up reviews. It is held by an administrator for Reviews & approvals. Anyone else cannot see the page.
- At least one custom field to build a rule on. See Custom fields.
- The approvers need access to the files they will decide on, or you can give them access to the request itself. An approver does not need write access to a file for a rule to set a field on it.
What starts a request
A request can come from several places:
- A rule you make on this page. It watches custom fields, or the sharing that your shares hold for approval.
- A form that sends its responses for approval. See Form approvals and decision fields. Rules a form makes appear in your list as “from the form” and its name.
- Publishing approval on a storage area, where changes to spreadsheets and documents wait for sign-off. See Publishing approval for spreadsheets and documents.
- Captur checks and MaSH scripts, which can raise a request of their own.
All of them arrive in the same place for the approver.
The Reviews & approvals page
Open Foldr Settings and choose Reviews & approvals under Governance. It has five sections:
- Overview: counts of requests that are Open, Overdue and Escalated, how many were Approved (30 days) and Rejected (30 days), the Avg. time to decide and Open by type.
- Inbox: every request waiting right now. See The Inbox.
- Rules: where you make rules.
- Sharing policy: which sharing needs approval, for everyone, for a user or for a group. A share can also say Never, which only an administrator for Reviews & approvals can choose.
- Dismissed: classification suggestions that were dismissed or blocked, with Allow again to clear one.
Make a rule
- Choose Rules, then Add rule.
- Under Rule name, give it a name the approver will recognise. It is the line they see under the file name. For example, “Expense claims over £500”.
- Under What this rule approves, choose Files whose field values match or Sharing that needs approval. The rest of this section describes the first. A sharing rule decides who approves sharing that a share already holds for approval.
- Under When, build the condition with the builder, or type it. For example, Claim amount greater than 500. Add more conditions to require all of them, or any of them.
- Under Only on these shares, pick the shares the rule covers. Leave it empty to cover every share.
- Set up the steps, the deadline and the outcome, as below.
- Choose Save.

A request is raised when a user changes a field and the rule’s condition becomes true. If the value changes again while the request waits, the request updates. If the condition stops being true, the request is withdrawn. There is one open request for each file and rule.
To stop a rule without losing it, switch Enabled off in the list. Rules run in order of Priority (lower runs first), which you set under Settings at the foot of the rule.
Steps and approvers
A rule has one Step or more. Choose Approval step in the Add bar to add another. Each step is finished before the next starts, and the arrows move a step up or down.
For each step, choose who approves:
- Any reviewer for the share: any of the default approvers, or users given the Review approvals permission on that share.
- Specific users or groups: pick them.
- The user named in a field: choose a field that holds a user. Foldr works out the approver when the request is raised. If the field is empty, or names a user who no longer exists, the request goes to any reviewer for the share. The user who raised the request is never their own approver.
With more than one approver, Approval needed sets the bar: Any one of them, Every one of them or A set number of them. The last one asks How many must approve.
From the second step on, Only require this step when adds a condition. If it is not true when the step before is approved, Foldr skips the step. The first step always applies.
Fields the approver fills in
Under a step, Fields the approver fills in lets the approver set a value on the file while they decide, such as a cost centre.
- Choose Add a field.
- Tick Required if Approve must stay disabled until the field has a value.
- Tick Also ask when rejecting to ask on a rejection too.
- Optionally set a Default value (optional). A people field has none.
The values are written to the file. See Form approvals and decision fields for the types an approver can set.
What happens on approve or reject
When a step is approved, When this step is approved can run actions straight away. Below the steps, On approve runs once the whole request is approved, and On reject runs when it is rejected. Choose Add action for each. An action is one of:
- Set a field on the file.
- Send a notification, to the user who raised the request, to email addresses you give, or both.
- Run an automation, which receives the file and the decision details.
Field writes use system authority, so the approver does not need write access to the file. If an action fails, Foldr records it, carries on with the others and shows Retry to the approver under Recently decided. A failed action never undoes the decision.
For a rule on files, Write the outcome to field puts the outcome wording, such as “Order not placed”, into a field on the file once the actions have run.
Below On approve and On reject, the switch Tell the requester the outcome is on by default. While it is on, the user who asked gets an email and a notification when the request is approved or rejected. Switch it off if the rule already says it another way. A Send a notification action that includes the requester does not send them a second message. A request that no user raised, such as one from a Captur check or a script, has nobody to tell.


Deadline and escalation
Choose Deadline in the Add bar.
- Set Hours until due.
- Optionally switch on Remind approvers and set Remind them this many hours before it is due. A new deadline has the reminder on: 24 hours before, or half the time if the deadline is under 48 hours. The number must be a whole number of hours, at least 1 and less than the hours until due. Rules you made before reminders existed have it off.
- Under When overdue, also ask, pick users or groups. You can also choose And the user named in a field.
When the time passes, Foldr adds those approvers to the step and emails them that the request has been escalated to them. It does that once. It never rejects a request for you. The request shows Overdue to the approvers until it is decided. A sharing request that is still waiting after 14 days lapses, and nothing is shared.
The same list is who an approver can hand a request to by hand. An approver sees Escalate next to Pause only on a rule that has people under When overdue, also ask (or a field under And the user named in). Without them there is nothing to escalate to, and the button is hidden. It is also hidden when the list would reach nobody new: Foldr leaves out the user who asked, the approver escalating, users or groups that no longer exist, and anyone already deciding the request. Handing it over removes it from the approver’s list and makes it the escalation list’s to decide.
The reminder is sent once. Foldr emails the approvers still to decide on the current step, and sends them a notice, that the request is due soon. It is not sent if the request is paused, escalated or already decided.
A paused request does not count down. See Approving requests in Foldr.
Settings
Under Settings, Notify approvers when it’s their turn sends them an email and a notice. Leave it on unless the approvers watch the inbox anyway.
Default approvers
On the Rules page, Default approvers lists the users and groups who decide requests sent to “any reviewer for the share”. They can act on the shares they can already open. To make someone an approver for one share only, grant Review approvals on that share’s access list instead.
The Inbox
Inbox lists every request waiting in your Foldr, whoever it was sent to, with the file, the share, the request and its age. Approvals holds requests from rules, forms and publishing. Classifications holds suggested labels from Governance.
Approve and Reject are here too. If a request is paused, it shows who paused it and why, and Approve or Reject asks first: Decide a paused request? with the reason, then Decide anyway?. That is so nobody overrides an approver who is waiting on something without knowing.
If something does not work
- A rule does nothing. Check the rule is Enabled, the condition matches the value, and Only on these shares includes the share. Only a change by a user starts a request. Values written by a crawl do not.
- An approver sees the request but cannot open the file. Give them Review approvals on the share, or access to it.
- The rule’s approver field is empty. The request goes to any reviewer for the share. Check the Default approvers.