Modules
Approvals and automations in Studio
Add approval rules to a custom module, see how a decided amount is held, work the Approvals inbox, handle documents attached to an approved record, and learn what automations and the Agent may and may not decide.
A custom module built in Studio can hold a move between stages until an approver decides. It can also run automations when records change. This page explains both, and where a person must always decide.
Approval rules
An approval holds one move of the module's workflow until an approver decides. It holds that move on every path: the record page, the API, and automations. Nobody approves their own record while someone else could.
A module needs a workflow with stages to have an approval. Add one, with waiting, approved, and rejected stages, in Edit details, or ask for it in the chat. Then open the module in Studio and go to Approvals, where New approval starts a rule:
- Name, for example Approve costly repairs.
- Waits at, Approved goes to, and Rejected goes to: three different stages.
- Who approves: A role (Managers, Super Admins, or both), Named people (up to two managers or admins who can open the module, with a Super Admin able to step in), or The line manager of whoever created the record, with a choice of what happens when they have none.
- Only if: a condition on a field, for example a cost over a limit. Amounts are in the workspace currency, so 1000 means 1,000.00.
To ask two people in order, add a stage between them and an approval for each move. Every rule a move passes is asked. If two rules gate the same move, each one applies, and the record waits for the people each rule names.
Once an approval decides a record, its approved stage and the stages after it count as decided. The only way into them is that approval's own decision, made from its waiting stage:
- A move from anywhere else that would land past an approval is refused: "This move goes past the approval {rule} without its decision. Move the record to {fromState} first, so it can be decided there."
- One move decides one approval. Below a Super Admin, a move that would decide more than one is refused: "This move would decide more than one approval at once, and below a Super Admin a move decides one. Ask a Super Admin to make it."
- Moves between decided stages are free. A move back before the approval undoes it, and the record is decided again on its way forward.
- An approval's own reject is never held up by a later approval, and moving a record to a final stage to cancel it decides nothing, unless that move is itself another approval's decision.
- A Super Admin can move a record past several approvals only where they may decide each one and nobody else would have to.
A record that is already past an approval when the approval is added, switched on, or changed to cover it counts as decided, and its decided amounts stay fixed.
Studio's change list also warns when a new or switched on approval decides a move that another approval's stage needs, so a record held there needs its decision too.
Studio reads every approval rule of a module before it judges a change. A module with more than 5,000 approvals, on or off, is refused until it is tidied. Contact Agaro support.
The rule's summary reads, for example, "From Submitted to Approved, by Managers. A rejected record goes to Rejected." Studio warns when a move lets a record skip an approval, for example a move to a stage where it ends with no decision.
An amount that was decided stays fixed
Once a record reaches the approved stage, the decision stands on every stage past it, not only the approved one. The values the decision was made on do not change underneath it.
- Calculated fields keep the value they had when the record was decided, and the field says Held as approved.
- A person who changes a field the approval reads, on a record that is already approved, sends the record back for a new decision. The record says so: "This record is {stage}, and its values changed since that decision. Save them on the record first: it goes back for a new decision."
- Some changes only an approver may make. The page says: "Only an approver can change {field} on it now. Move it to {stage} first, so an approver can decide it in Approvals."
- A new record cannot start at a stage an approval decides.
The Approvals inbox
Approvals lists the requests waiting for a decision. A record waiting at an approval rule's stage appears there for its approvers, who can Approve it, which moves it to the approved stage, or Reject it with a note, which moves it to the rejected stage. The inbox is for Managers and Super Admins. A module's page also has a Waiting in Approvals link.
- A record changed since you opened the inbox asks you to review it again before you decide.
- You cannot approve a record you made or changed when someone else can, and one person cannot decide two approvals of the same record in a row.
- If nobody allowed to decide an approval can approve the record, it says "Nobody who may decide the approval {rule} can approve this record now. A Super Admin has to change the approval in Studio."
- The inbox only offers a record to you when you can decide it.
- If more records wait under rules than the list can read, the inbox says how many more and sends you to the module.
Documents attached to an approved record
A document attached to a record follows the record's decision.
- Changing an attached document, for example adding a version, sends the record back for approval.
- A document with no published version cannot move forward until a Super Admin publishes one. It can be rejected in the meantime.
- On a finished record, one where nothing moves on from the final stage, the documents attached to it stay as they are. Only a Super Admin may change one. The record keeps its stage and its values, and gets a line in its history, such as "While this record was Approved, a Super Admin added a new version of the attached document {document}."
- If a document has to change on a finished record, a Super Admin adds a way back to the workflow in Studio.
Who can change a module that holds a decision
Below a Super Admin, a module whose records can reach a decided amount cannot change its shape or its workflow. While an approval stands on a module, or on one it reads, its workflow, calculated fields, relations, field types, and option values stay as they are, and no field is removed. A Super Admin makes the change. In the same way:
- Below a Super Admin, an approval can only get stricter. Ask a Super Admin to turn off or loosen one.
- Below a Super Admin, the first approval on a record type can be added, but a second one cannot: "An approval beside existing ones is added or switched on by a Super Admin." Approvals shape each other's decided stages, so when a Super Admin adds one, the review names every other approval it changes.
- A rule cannot name the person writing it as its approver. Choose someone else, or ask a Super Admin.
- Only a Super Admin can undo a change that would loosen or switch off an approval.
Automations and approvals
Rules that run when a record changes are listed under Automations in the module. They are the same workflows the Automations module edits, and a rule runs as whoever turns it on, with their access.
- An automation cannot decide an approval. The record waits in the Approvals inbox until an approver decides it.
- An automation cannot change a money field, or a field an approval reads. A person changes it on the record.
- An automation cannot change a record that is held at a stage an approval decides.
- An AI step never approves, rejects, or decides anything.
- A step a person placed may decide things that are not money. A step that records a payment needs a maximum amount saved on it, and a payment above it is left to a person. Other decisions about money are left to a person. A refused step reads "A person decides this. An AI step never approves, rejects or decides, and a workflow step decides money only up to the maximum saved on it."
- The Agent cannot decide an approval on its own either. An approver decides it in the Approvals inbox.
Studio buttons run for the person pressing
A button in a module runs its workflow for the person who presses it, using steps that another person placed when they published it. So that a button cannot show a person records they could not open themselves, record access follows the presser and every person who placed a step on the chain of workflows the button runs.
- When that check fails, the step is refused with a message saying so, and values are withheld: the workflow receives the record's id, not its values.
- In a run's history, the full data (what each step read and returned, and an error's description and details) is shown to a Super Admin, to the person the run was for, and to the person who placed the button's steps when they pass the same check. Everyone else sees a summary: the steps, their statuses and timings, and an error's code and message.
Credentials and HTTP requests in automations
A saved credential, such as a bearer token or header key, can only be sent to an address it has already been used with.
- Only the person who saved its secret, or a Super Admin, can use it with a new address. Their first use records the address.
- Anyone else is refused: "This credential has not been used with this address. Only the person who saved its secret, or a Super Admin, can send it to a new address."
- Credentials saved before 8 November 2026 need their secret typed again, or one run by a Super Admin, before a Manager's workflow can send them to a new address.
- An HTTP request that carries a credential does not follow a redirect to a different address.
- A step cannot set a cookie header.
Troubleshooting
My move says it needs an approver's decision
The record is waiting for the approval rule. It appears in the Approvals inbox, and an approver decides it there.
I cannot change a field on an approved record
The approval reads that field. Only an approver can change it now, or you can move the record back to the earlier stage so an approver can decide it again.
I cannot change the workflow of a module
An approval stands on the module. A Super Admin makes that change.
A later approval says only a Super Admin can decide it
The message reads "Who decided an earlier approval of this record is not on record, so only a Super Admin can decide {rule} on it." Agaro checks that one person does not decide two approvals of the same record in a row, and for records approved before the evening release of 7 November 2026 it cannot tell who made the earlier decision. A Super Admin decides it this time. Once the record goes through its approvals again, everyone who may decide can do so as usual.