> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/platform-bloxchain.app/overview-1/allowlists.md).

# Allowlists

**Audience:** Admin · **App path:** sidebar **Allowlists**

Restrict where guarded operations may send value or which **contracts** may be called. Empty list = **deny all** for that selector.

## Three list types (sidebar)

| Nav item             | Use for                                                                                                                                                                        |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Recipients**       | Native transfer destinations ([treasury](/platform-bloxchain.app/use-cases/treasury.md))                                                                                       |
| **Payees**           | Attached-payment / payee-specific selectors                                                                                                                                    |
| **Contract targets** | Token contracts, routers, dapp contracts ([token ops](/platform-bloxchain.app/use-cases/token-ops.md) · [external calls](/platform-bloxchain.app/use-cases/external-calls.md)) |

## Add an allowed address

1. Open the list type above.
2. **Add target** (or equivalent) — form fields:

| Field                    | What to enter                                                                   |
| ------------------------ | ------------------------------------------------------------------------------- |
| **Function / operation** | Selector tied to the operation you registered (dropdown lists eligible schemas) |
| **Address**              | `0x…` — recipient EOA, payee, or contract target                                |

3. **Sign** → **Execute** guard-config batch.
4. Repeat for every address your policy must allow (batch up to 10 per submit in the UI).

![Allowlist — placeholder](/files/47PrqJi0UtraG3zSn71s)

After allowlists, complete [Connect your application](/platform-bloxchain.app/overview-1/connect-your-application.md).

## Verify it worked

* [Submit request](/platform-bloxchain.app/overview/submit-request.md) to an allowed target succeeds.
* Disallowed target reverts on-chain with allowlist error.

## Common issues

* **Recipient not in dropdown on New request** — address missing from **Recipients** allowlist for native transfer selector.
* **External call reverts** — router/pool/proxy not on **Contract targets** for `execute(bytes)`.

## Next steps

* [Execution ports](/platform-bloxchain.app/overview-1/execution-ports.md)
* [Guard controller](/protocol/guard-controller.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloxchain.app/platform-bloxchain.app/overview-1/allowlists.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.