# Approval for all (setApprovalForAll)

> A transaction that lets an operator manage every token you hold in one NFT or multi-token collection contract.

- Request: `setApprovalForAll(operator, true)`
- Standard: ERC-721 and ERC-1155
- Track: Request types
- Checked against sources: 2026-11-04
- Review status: drafted with AI assistance, awaiting human review
- Canonical page: https://walletpermissions.com/learn/requests/set-approval-for-all

Education only. This does not assess any real request, wallet or app, and is not advice to sign or not sign. Every app, token and address in the practice card is fictional.

## What to read in the prompt

- The collection contract the request is sent to.
- The operator: the address that receives the right.
- The true or false value: `true` grants the right, `false` removes it.

## What it lets the other party do

- ERC-721: “Enable or disable approval for a third party (“operator”) to manage all of `msg.sender`’s assets.” ERC-1155: “Enable or disable approval for a third party (“operator”) to manage all of the caller’s tokens.”
- The operator can transfer your tokens in that contract. Because the approval is an on/off switch for the operator, not a list of token IDs, it covers whatever you hold in that contract when the operator acts.

## What it does not do

- It covers one contract only, not your other collections.
- It does not transfer anything by itself, and it sets no price or amount limit.

## How long it lasts

- Neither ERC-721 nor ERC-1155 defines an expiry. It stays on until you call `setApprovalForAll(operator, false)`.

## How to undo it

- Send `setApprovalForAll(operator, false)` to the same collection contract. It does not return tokens that already moved.
- Check your real approvals with Revoke.cash or Etherscan’s token approval checker.

## A pattern to recognise

- Marketplaces can ask for this when you list, so the prompt can look routine. A “free mint” or “claim” page asking for it on a collection you already own deserves a second look at the operator.

## Practice question (fictional)

You want to list one fictional Paper Heron for sale on fictional Kiteframe Market. You hold six herons.

| Field | Value |
| --- | --- |
| Request type | Transaction: setApprovalForAll |
| Collection | Paper Herons (fictional ERC-721) |
| Operator | Kiteframe Transfer Helper (fictional contract) |
| Value | true |
| You hold | 6 herons |

**Question:** Does this request cover only the one heron you plan to list?

**Answer:** No. Approval for all covers every token you hold in the Paper Herons contract, including the other five, until you switch it off.

## Check your real account elsewhere

This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements):

- [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks
- [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet

## Sources

- [ERC-721: Non-Fungible Token Standard](https://ercs.ethereum.org/ERCS/erc-721). Ethereum ERCs. Final; created 2018-01-24. Checked 2026-11-04.
- [ERC-1155: Multi Token Standard](https://ercs.ethereum.org/ERCS/erc-1155). Ethereum ERCs. Final; created 2018-06-17. Checked 2026-11-04.
