> 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/connect-your-application.md).

# Connect your application

**Audience:** Admin / integrator · **When:** After policy is configured

Make **enforcement real**: the addresses that request, sign, and execute must match what you configured on the Account workspace. Your **application** (EOA, backend wallet, or contract) must align with roles, operations, and allowlists.

## Two addresses to keep straight

| Address               | Role in docs                                                                             |
| --------------------- | ---------------------------------------------------------------------------------------- |
| **Account workspace** | The contract tab in bloxchain.app (`/dapps/:id`) — where policy lives                    |
| **Your application**  | Token contract, router, agent wallet, or automation contract that **uses** the workspace |

The SDK and integrations use the **Account workspace address** as `contractAddress`. Business logic may live in other contracts that appear on **allowlists** or as **members**.

## Three connection points

### 1. Members (who may act)

**Deployment → Members** assigns wallets **or contract addresses** to roles.

| Actor                  | Typical assignment                                        |
| ---------------------- | --------------------------------------------------------- |
| Human operator         | EOA                                                       |
| Backend / agent signer | EOA with **sign** permission (not broadcaster)            |
| Automation contract    | **Contract address** as member if it is the logical actor |

[Roles & members](/platform-bloxchain.app/overview-1/roles-and-members.md) · [Permissions](/platform-bloxchain.app/overview-1/permissions.md)

### 2. Operations (what may be requested)

Register every **function schema** your app will invoke through the Account. If an operation is missing, requests fail before allowlists matter.

[Operations](/platform-bloxchain.app/overview-1/operations.md)

### 3. Allowlists & contract targets (where calls may go)

**Allowlists** restrict recipients, payees, and **contract targets** per execution selector.

| Target type           | Example                                    |
| --------------------- | ------------------------------------------ |
| **Recipient / payee** | Employee wallet for treasury               |
| **Token contract**    | ERC20 your vault pays out                  |
| **External protocol** | Router, composer proxy, your dapp contract |

[Allowlists](/platform-bloxchain.app/overview-1/allowlists.md) · [Execution ports](/platform-bloxchain.app/overview-1/execution-ports.md)

> Protocol detail: calls to `address(this)` on the Account are allowed for internal/composed execution without whitelisting the Account on every selector — see [Guard controller](/protocol/guard-controller.md).

## Typical wiring flow

1. Finish [configure](/platform-bloxchain.app/overview-1.md) or a [use case guide](/platform-bloxchain.app/use-cases.md).
2. Whitelist your **token** or **router** under the correct selector.
3. Add your **service wallet** or **contract** to **Members** with the right role.
4. Point your app / SDK at the **Account workspace address**.
5. Submit a test [request](/platform-bloxchain.app/overview/submit-request.md); verify [My access](/platform-bloxchain.app/overview/my-access.md) for the signing wallet.

## Signer vs broadcaster (meta-tx)

For meta-transaction paths:

* **Signer** — often an agent or approver wallet (EIP-712)
* **Broadcaster** — separate wallet with protected role; executes from **Signed** queue

They must be **different addresses**. See [Approve and sign](/platform-bloxchain.app/overview/approve-and-sign.md) and [Security settings](/platform-bloxchain.app/overview-1/security-settings.md).

## Troubleshooting

| Symptom              | Check                                                                                                                             |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Operation not listed | [Operations](/platform-bloxchain.app/overview-1/operations.md) + [Permissions](/platform-bloxchain.app/overview-1/permissions.md) |
| Allowlist revert     | [Allowlists](/platform-bloxchain.app/overview-1/allowlists.md) for that selector                                                  |
| Wrong actor          | [Members](/platform-bloxchain.app/overview-1/roles-and-members.md) — connected wallet vs assigned address                         |
| SDK errors           | [Developers — deployment](/developers/deployment.md) · [SDK authentication](/developers/sdk-authentication.md)                    |

## Next steps

* [Use a contract](/platform-bloxchain.app/overview.md) (member handoff)
* [Production readiness](/developers/production-readiness.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/connect-your-application.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.