> For the complete documentation index, see [llms.txt](https://docs.squads.so/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/main/navigating-your-squad/transactions.md).

# Transactions

How to initiate and execute various transaction types within your Squad.

{% embed url="<https://www.youtube.com/watch?v=_Jv1arm7Efk>" %}
How transactions work inside Squads
{% endembed %}

### How transactions work inside Squads

Transactions are a key element of the Squads platform. They are initiated whenever a Squad member performs an action requiring approval from other members.

#### Transaction States

Transactions can exist in one of three states:

1. **Active**: Pending signatures from other Squad members to reach the confirmation threshold.
2. **Ready**: Confirmation threshold met; the transaction is now executable.
3. **Canceled**: Transaction terminated by Squad members or due to changes in Squad parameters.

### **Transactions tab**

The "Transactions" tab provides a chronological display of all Squad transactions. It enables users to:

* Change [priority fees ](/main/navigating-your-squad/transactions/priority-fees.md)for transactions
* Use [batch actions](/main/navigating-your-squad/transactions/batch-actions.md) to execute transactions in bulk
* [Reclaim rent](/main/navigating-your-squad/transactions/rent-reclaim.md) for executed transactions
* [Approve/reject transactions](#how-to-approve-reject-transactions)
* [Execute/cancel transactions](#how-to-execute-cancel-transactions)

<figure><img src="https://254049203-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdUrslJzNhqr2JDZzXUUz%2Fuploads%2FWlkgQFajp2e2FM3pB66t%2FTransactions%20list.png?alt=media&amp;token=726fed9a-287c-4eea-ae95-dca18cdc3b2e" alt=""><figcaption><p>Transactions tab</p></figcaption></figure>

### **How to approve/reject transactions**

Any action (e.g., member management, token transfers, program upgrades) initiates a transaction in the "Ready" state. It only executes once the Squad's confirmation threshold is met. The initiating member automatically confirms the transaction.

<figure><img src="https://254049203-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdUrslJzNhqr2JDZzXUUz%2Fuploads%2FGU9MTgahZSGBisLFMoc9%2FActive%20tx%20epxanded%20NEW.png?alt=media&amp;token=4ce4c1eb-c5ef-4c52-839c-b9165f7e2ede" alt=""><figcaption><p>Active transaction. Expanded view</p></figcaption></figure>

Other members can approve or reject transactions by:

* Expanding the transaction in the list view
* Clicking "See details" for a comprehensive view

<figure><img src="https://254049203-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdUrslJzNhqr2JDZzXUUz%2Fuploads%2FqQSnWC1GgEadvc3RJiZw%2FTransaction%20detailed%20active.png?alt=media&amp;token=80f57d79-4fe9-4c04-84e0-d5ed14b97b63" alt=""><figcaption><p>Detailed view</p></figcaption></figure>

### **How to execute/cancel transactions**

Once the confirmation threshold is met, a transaction in the "Ready" state can be executed or canceled based on the signatures of other Squad members.

* **Execution**: Once the confirmation threshold is met, any Squad member can execute the "Ready" transaction.
* **Cancellation**: Requires reaching the confirmation threshold for canceling the transaction.

<figure><img src="https://254049203-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdUrslJzNhqr2JDZzXUUz%2Fuploads%2FcA8ykGSRVMs27WAJdnnn%2FReady%20tx.png?alt=media&amp;token=2979dcee-47c9-41eb-864c-f0b1f291c7bc" alt=""><figcaption><p>"Ready" transaction</p></figcaption></figure>

{% hint style="info" %}
Learn how to export your transactions as a CSV in our guide [here](broken://pages/GJz3IXqBMYqb2o2gDGYN).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.squads.so/main/navigating-your-squad/transactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
