Approvals
Approvals that end
in a signature
Route every payout through the people allowed to approve it, then collect the Safe signatures that actually move the money — one path, one record.
Non-custodial. WorkTGT never holds your keys.
The gap
Approval and execution live in two different places
Most teams approve spending in a chat thread and sign it in a wallet. Nothing connects the two, so the record of who agreed is not the record of what moved.
Approval in chat
A thumbs-up in a group chat is not an authorisation. It cannot be revoked, it disappears down the scrollback, and it never names which transaction it approved.
Signing in private
The signer opens their wallet alone. Whether the transaction they signed is the one that was agreed is something nobody else is in a position to check.
No trail either way
When someone asks who approved a payment last quarter, the answer is a screenshot — from a channel that anyone with admin rights could have edited.
How it works
One path from request to on-chain settlement
Each stage has a named owner and leaves a record that outlives the people in it.
- 1
A request is raised
The requester names the recipient, the amount and the project it belongs to. The address comes from an address book an admin controls, not from a paste into a form.
- 2
Approvers decide
Only the roles you assign can approve, and the assignment is per project. An approver sees the whole request — amount, destination, memo, history — before deciding.
- 3
Safe signers sign
An approved request becomes a Safe transaction needing M of N signatures. No single signer can move funds on their own, and WorkTGT is not one of the signers.
- 4
The chain confirms
Execution happens on-chain and the transaction hash is written back to the request, so the approval record and the settlement record are the same record.
Questions about approvals
Does WorkTGT hold the keys to our Safe?
No. Signing happens in each signer's own wallet, and the Safe's owners are addresses your team controls. WorkTGT can read the Safe and prepare transactions for it; it cannot sign for it.
Can approval rules differ per project?
Yes. Approvers are assigned per project, so a marketing budget and a payroll account can require different people to sign off without needing two separate Safes.
What happens when an approver leaves?
Remove their role and they can no longer approve, immediately. Past approvals stay in the audit log under their name — removing someone must not rewrite what they already decided.
Do we still need the Safe interface?
Only if you want it. Safe remains the contract of record and you can always transact against it directly; WorkTGT adds the request and approval layer in front of it.
Move your team's money
transparently, starting today
Start free without a credit card. Setup takes five minutes, and your funds stay inside your team's Safe.