Approve what your team sends

Every change to your lots waits for a person's approval: registering a harvest, a delivery, a processing step, a certificate, a status change. Approvals keep a second pair of eyes on what reaches the ledger, whoever asked for it: a colleague, the assistant, an automation or another system.

How an approval reads

Open Approvals. Five tabs, each with its count, sort the requests: Needs your approval (what you can decide), In progress (approved and being signed or recorded, or waiting for someone else's decision), Completed (recorded on the ledger), Didn’t go through (rejected, expired or failed, with the reason) and All. Each row starts with what happens, as one sentence, and shows its step, such as "Step 3 of 5 · Signatures":

Deliver 12.5 t of Soybeans lot SOY-2026-014 from Fazenda Boa Vista to Armazém Serra Azul

Select a row to review it. The panel shows, in this order:

• Requested by: the person, and the channel when it was not the console ("Ana · via the assistant").
• Note from the requester: why they asked.
• What it affects: the lot, quantities in the lot's unit, from and to, and any change shown as before and after.
• Before you approve: the risks, such as "Only the receiver can send the goods back". A tag sums them up: High impact, Check carefully or Routine.
• The approval steps: the rule, and the steps done and still to come.
• Technical details: kept closed. You never need them to decide.

When the assistant or another AI tool drafted it, a warning asks you to check every value against your records.

Who can approve

The rule usually says that one member with approval rights, other than the proposer, gives the approval with two-factor verification.

• Owners, admins, operators and approvers have approval rights.
• Nobody can approve what they asked for, except an owner on something they asked for in the console.
• Changes prepared by A-REX operations, and changes to your administration account, are approved by the owner only. The owner's device then asks for the owner passkey.
• What automations propose is approved by owners and admins by default. The owner can change that in Settings › Automations with Edit approvers. The person who published the automation does not approve its proposals (one exception for lot rule changes). See Proposals from automations.

Proposals from automations

An automation never approves anything: what it proposes waits in Approvals like any other request.

• Requested by the automation names it and its version, with See the run to open the run that prepared it.
• When a value was calculated, for example tonnes of CO₂e from the lot quantity and a company value, How the values were computed shows the formula with the real numbers. See Company values.
• A step set to repeat For each lot it names prepares one proposal per lot, never two for the same lot.
• The roles that approve each kind (Status changes, Attestations, Lot rule settings, Add-on records) are set in Settings › Automations.
• The member who published the automation never approves what it proposes. One exception: a change of lot rules proposed by an automation, when the publisher is the only member who may approve it. The panel then says "You published the automation that proposed this; nobody else in your company can approve it", and the decision is recorded as such in the audit log.

The approver role

Approver is a role for people who check without creating: they read everything and approve what others propose, but never create anything themselves. It suits a quality manager or a partner in the business who signs off. See Roles.

Approve or reject

1. In Approvals, select the row and read the panel.
2. Optionally write a Reason (optional). It is recorded in the audit log with your decision.
3. Select Approve or Reject. A message says where it went, for example "Approved · now in In progress", with Show it.
4. In Confirm it is you, type the 6-digit code from your authenticator app and select Verify and continue.

To decide several at once, select the rows and use Approve or Reject in the toolbar. The confirmation lists each sentence again. An approval nobody decides expires after 72 hours and shows Expired without a decision.

After approval the platform carries it out, and the last step turns to Recorded on the ledger. Some approvals wait for one more step first, such as "Waits until the receiver is allowed". See Waiting states.

Low-risk auto-approval

The owner can let low-risk actions, such as registering a harvest or a delivery between your own sites, be approved automatically. The person who sends one then sees It was approved automatically and is being recorded. Actions proposed by automations or by other systems are never approved automatically.

Two-factor on every decision

Each approval or rejection asks for a fresh code, even if you signed in a minute ago. Without an authenticator app you cannot approve: set it up in Your sign-in.