> 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/operations.md).

# Operations

**Audience:** Admin · **App path:** Deployment → **Operations**

Register **function schemas** — the operations members can request. Each schema defines a function signature, a display name, and which **workflow steps** (request, approve, sign, execute) the operation supports.

Use-case recipes with copy-paste values: [Use cases & quick setup](/platform-bloxchain.app/use-cases.md).

## Register a new operation

1. Open **Deployment → Operations** → **Register operation**.
2. Fill the form:

| Field                     | What to enter                                                                                                               |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Operation name**        | Short label shown in **New request** (e.g. `Native Transfer`)                                                               |
| **Function signature**    | Exact ABI string (e.g. `__bloxchain_native_transfer__()` or `transfer(address,uint256)`) — must match the on-chain selector |
| **Workflow capabilities** | Click a preset or toggle steps on the diagram (see below)                                                                   |

3. **Sign** the guard-config meta-transaction, then **Execute** to submit on-chain.
4. Confirm the operation appears in the operations list.

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

### Workflow capability presets

| Preset                     | Typical use                                                                  |
| -------------------------- | ---------------------------------------------------------------------------- |
| **Meta request + approve** | Requester submits; approver signs and finalizes (treasury, vault, token ops) |
| **Meta approve**           | Approval-only path (often with a **Broadcaster** for finalize)               |
| **Time-delay**             | Waiting period before approval can finalize                                  |
| **Meta cancel**            | Governed cancellation path                                                   |
| **All actions**            | Full surface — only when you need every step                                 |

Enabled steps define what you can assign in [Permissions](/platform-bloxchain.app/overview-1/permissions.md). Steps you leave off cannot be granted to roles.

### UI step labels → permissions

When granting permissions per role, the app uses these labels (maps to on-chain TxActions):

| Label in app              | Role in flow                                                    |
| ------------------------- | --------------------------------------------------------------- |
| Pending Request           | Member starts the operation                                     |
| Sign and approve request  | Approver reviews and signs                                      |
| Finalize approved request | Submits the approved operation on-chain (often **Broadcaster**) |

See [How this works](/introduction/operational-model.md) for timelock vs meta-transaction paths.

## After registration

| Next                                                                       | Why                                               |
| -------------------------------------------------------------------------- | ------------------------------------------------- |
| [Roles & members](/platform-bloxchain.app/overview-1/roles-and-members.md) | Create roles and assign wallets                   |
| [Permissions](/platform-bloxchain.app/overview-1/permissions.md)           | Grant request / approve / sign / execute per role |
| [Allowlists](/platform-bloxchain.app/overview-1/allowlists.md)             | Restrict recipients or contract targets           |

## Verify it worked

* Operation appears in the list and in SDK schema reads.
* After permissions are set, a test wallet sees it under [My access](/platform-bloxchain.app/overview/my-access.md).

## Common issues

* **Signature mismatch** — function signature string does not match the selector your contract uses; re-check ABI.
* **Operation missing for operators** — permissions not set ([Permissions](/platform-bloxchain.app/overview-1/permissions.md)).
* **Stuck after sign** — connect a wallet with **Finalize** permission on guard-config batch, or use **Broadcaster** per [Security settings](/platform-bloxchain.app/overview-1/security-settings.md).

## Next steps

* [Set permissions by operation](/platform-bloxchain.app/overview-1/permissions.md)
* [Use cases & quick setup](/platform-bloxchain.app/use-cases.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/operations.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.