Requires Action
Requires Action is the list of everything in your organization that is waiting on you: payments to approve, sign or send, and requests from teammates for access. You decide each one from the same screen, without hunting through the payments list.
It’s the first row in the sidebar, Requires Action. The number beside it is how many items are waiting on you.
Why use it
Section titled “Why use it”Money that needs several people to move it stalls when nobody knows it’s their turn. Requires Action shows each person only what they can act on now:
- A payment waiting for an approval you can give, under your organization’s approval policies.
- An approved payment that needs its Safe transaction proposed, signed or executed.
- A payment made outside Mezzanine, such as a bank transfer, that someone has to confirm was paid.
- A teammate asking for a permission, or for access to a single company file.
You see what is being asked, who asked, and what has already happened, before you decide.
How it works
Section titled “How it works”- Someone submits a payment for approval. Its amount picks a tier of your approval policy, which says how many approvals it needs and who can give each one. Drafts never appear here.
- Approvers click Approve. Each person’s approval fills one of the tier’s approvals. When the last one is in, the payment moves to execution.
- If the money comes from a Safe, someone proposes the transaction. This creates the Safe transaction. A proposer who is a Safe owner signs it at the same time.
- The Safe’s owners sign it until the Safe’s own threshold is met.
- Someone executes it. Mezzanine sends the signed transaction on-chain, and the payment completes when it’s confirmed.
If the money comes from an account Mezzanine doesn’t send from, step 3 onwards is replaced by one step: someone the Off-site accounts execution policy names pays it there and clicks Mark executed. If that policy asks for more than one confirmation, each of them marks it, and the payment completes when the last one is in.
If a Safe payment was already sent from the Safe in another app, someone that policy names can click Mark executed beside Propose in place of step 3, the same way. Once a transaction is proposed from Mezzanine, the outcome on-chain decides instead.
For the click-by-click version, see Approve, sign and send a payment.
Using the page
Section titled “Using the page”The list
Section titled “The list”Tabs across the top narrow the list: All, Send Money and Permissions, each with a count, and History. The search box finds items by title, type or who sent it.
Each row shows the item’s title, what kind of item it is, and where it came from, such as Initiated by Jordan Chu · 2 hours ago
or Auto-generated by the Recurring Payments app
. A flag or document icon means one is attached. With Wallet Verification Mode on, a payment to a wallet that isn’t verified for it shows the flag too, counted with the others. Hover the flag to read each concern, the wallet’s first: Wallet not verified
, Network not verified for this wallet
or Asset not verified for this wallet
.
The pill on the right says what the item is waiting for:
| You see | What it means | What to do |
|---|---|---|
| 1 of 2 | The payment has 1 of the 2 approvals its tier needs | Open it and click Approve or Reject |
| Awaiting proposal | Approved, paid from a Safe, and nobody has created the Safe transaction yet | Click Propose |
| 1 of 2 signatures or Awaiting signatures | The Safe transaction exists and needs more owner signatures | If you’re an owner who hasn’t signed, click Sign |
| Ready to execute | The Safe transaction has all the signatures it needs | Click Execute |
| Awaiting confirmation | The transaction has been sent and is waiting for the blockchain | Nothing. It clears on its own |
| Awaiting completion | The payment is made outside Mezzanine and nobody has confirmed it yet | Pay it where the money is held, then click Mark executed |
| Confirmed on-chain or Failed on-chain | The transaction has landed. The row leaves the list when the payment updates | Nothing |
You’ve signed under the pill means your signature is in. The row stays so you can execute it once the other signatures arrive.
When nothing is waiting, you see All clear, nothing needs your attention.
The detail panel
Section titled “The detail panel”Click a row to open it on the right. For a payment you see:
- Amount, To, From and Execution. Execution says how the money will move, such as
Executed from Treasury Safe
orExecuted outside Mezzanine
. - A warning if something is wrong, such as Incomplete payment when a required field is empty.
- Details, which opens the full sending and receiving account details and the transaction fields.
- Flags and Documents attached to the payment. With Wallet Verification Mode on, a destination wallet that isn’t verified for the payment is listed first under Flags, marked
Added automatically
. It can’t be removed; it clears once the wallet is verified. With Start wallet verification, click Send a test transaction or mark it as verified in it. - Process: what has already happened and what still has to. Policy beside it opens the payment’s tier on Approval & Execution.
The buttons at the bottom:
| Button | What it does |
|---|---|
| Approve | Records your approval. You’re offered Add a document (recommended) first, then asked to confirm Approve this payment?. No money moves until the payment is executed. Greyed out if the payment’s tier doesn’t name you |
| Revoke | Takes back your approval while the payment is still waiting for others. It shows in place of Approve once you’ve approved |
| Reject | Ends the payment. Rejection is final — the payment can’t be approved afterwards.You can give a reason, which is kept for the audit trail |
| Propose, Sign, Execute | The next Safe step. Each opens a window that uses your connected wallet |
| Mark executed | Confirms a payment made outside Mezzanine was paid, or a Safe payment sent from the Safe in another app before anyone proposed it here. If others must confirm it too, you see Your mark is recorded. The payment settles once its other confirmations are in. |
| Mark failed | Records that a payment made outside Mezzanine wasn’t paid. This is final |
| Add flag | Adds a note every reviewer sees. It does not block or approve anything on its own.Up to 90 characters |
| Add document | Attaches a file or link to the payment’s record |
| More actions (…) | Share copies a link to the payment. Send back to edit returns it to Drafts. Edit details opens its form |
When a decision takes a payment out of your list, the next item opens. A payment you’ve fully approved stays open if it moves to execution, in case you’re the one to propose or sign it.
Permission and document requests
Section titled “Permission and document requests”A permission request shows who asked, the permission and what it allows. Under Grant via, choose Direct grant to give only what was asked for, or a group. Joining the group grants everything the group holds, not only this permission.
Then click Grant or Deny.
A document request is One-off access to a single file, not the whole series.
It’s decided the same way.
History
Section titled “History”Everything decided in your organization that you can see, newest first. Filter by kind (Send Money, Permissions, Document access) or by outcome (Approved, Rejected), or search by title, outcome, type or who decided. Click a row to see who decided, when and why.
For a payment, open Changes below Process to see its recorded activity, oldest first, with who made each change. This includes edits, documents, flags, decisions and execution. Click Load more to read later activity. You can still add flags or documents and share the payment; its decision is final.
Approval policies and Safe signers
Section titled “Approval policies and Safe signers”Two separate rules decide who must act on a payment.
Approval policies decide who approves it. They’re set on Approval & Execution: one policy for money leaving the organization, one for moves between your own accounts. The payment’s amount picks a tier, and the tier lists its approvals and who can give each one. A new organization starts with one approval, from Admin or Owner, at every amount. The same page sets who marks executed a payment from an account Mezzanine doesn’t send from.
The Safe’s threshold sets how many owner signatures the Safe transaction needs. Mezzanine reads it from the Safe itself, so if the Safe’s owners change it, the new number applies. To propose you need a wallet that is an owner or delegate of the Safe. To sign you need an owner wallet.
Good to know
Section titled “Good to know”- Drafts aren’t listed. A draft is its author’s until they submit it for approval, from its form or from Move Money.
- Once you approve, the payment leaves your list while it waits on the others. It comes back if it reaches execution and you can propose, sign or execute it.
- Signatures are per wallet. If you hold two owner wallets on the same Safe, you can sign with each.
- You can reject or send back a Safe payment only until its transaction is proposed. After that, the outcome on-chain decides. If the transaction is cancelled in the Safe, the payment ends as rejected.
- Earlier Safe transactions go first. If other transactions are queued ahead of this one in the Safe, Execute shows
Transaction not executable
until they are executed or rejected. - Every destination is screened against sanctions lists when the transaction is proposed and executed. A flagged address stops the payment with
The destination address didn’t pass sanctions screening, so nothing was sent. Don’t send funds to it.
- With Wallet Verification Mode on, an unverified destination shows a warning such as
Wallet not verified
. You must tickI understand this wallet isn’t verified for this payment and want to proceed.
before you can continue, and the exception is logged. With Start wallet verification, you can click Send a test transaction or mark it as verified in the warning instead (Verify a wallet with a test transaction, Verify a wallet manually). See Wallet Verification. - If a decision fails, you see
That didn’t go through. Nothing was recorded — try again.
If someone else acted first, you seeThis payment moved on — refreshed.
Who can use it
Section titled “Who can use it”Everyone in your organization can open Requires Action. What appears depends on what you’re allowed to decide.
| To… | You need |
|---|---|
| See payments here | View outgoing transfers. A payment waiting for an approval you can give is listed without it |
| Approve a payment | Be named in one of the approvals its tier still needs |
| Reject or send back a payment | Be named in its tier, or Propose bill payments for payments to others, or Propose internal transfers for transfers between your own accounts |
| Propose, sign or execute a Safe payment | Propose bill payments or Propose internal transfers, as above |
| Mark executed a payment made outside Mezzanine, or an unproposed Safe payment sent from another app | Be named in the Off-site accounts execution policy |
| Mark failed a payment made outside Mezzanine | Be named in that policy, or the propose permission, as above |
| Propose a Safe transaction | A connected wallet that is an owner or delegate of the paying Safe |
| Sign a Safe transaction | A connected wallet that is an owner of the paying Safe |
| Decide permission requests | Membership of the Admin or Owner group |
| Decide document access requests | Admin or Owner, or Manage company files |
If the payment’s tier doesn’t name you, Approve is greyed out, and so is Reject unless you hold the propose permission. Without the propose permission, Propose, Sign and Execute are greyed out too. Add flag, Add document and the More actions items still show, and clicking one tells you which permission is missing and lets you request it.