> For the complete documentation index, see [llms.txt](https://transactiontool.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://transactiontool.hedera.com/transactions/signing-transaction-s.md). # Signing Transaction(s) *** ### Prerequisites Before you begin, ensure you have: * **Organization Access:** You must be connected to an organization that sent the transaction for signature * **Signing Key:** Your key pair must be linked to your organization account(s) * **Correct Network:** Verify you are connected to the intended network before signing. Transactions submitted to the wrong network cannot be undone. *** ### Step 1: Know When You Have Transactions to Sign The Transaction Tool notifies you through multiple channels when a transaction is waiting for your signature. You do not need to constantly check the application. #### Email Notifications When a transaction is created and assigned to you as a signer, the tool sends an email to your registered address. The message includes the transaction type and the organization it belongs to. Click the link in the email to open the transaction directly in the app. You can customize which events trigger email notifications under **Settings > Notifications**. See Notifications for more detail. #### In-App Notifications Select the **bell icon** in the top-right corner of the application to open the notification panel. Notifications are organized into three categories: | Type | Description | | ----------------- | -------------------------------------------------------------------------------------------------- | | **Actionable** | Transactions requiring your immediate attention, such as a transaction waiting for your signature. | | **Informational** | Status updates, such as "signature threshold reached" or "transaction executed successfully." | A red badge on the bell icon shows the count of unread notifications. Clicking any notification navigates you directly to the relevant transaction and marks it as read. When multiple transactions need attention at once, the tool groups them by organization, network, and event type. Clicking a grouped notification automatically switches your active organization and network context and takes you to the correct view. #### Ready to Sign Tab The most direct way to see everything awaiting your signature is the **Ready to Sign** tab on the Transactions screen. * Select **Transactions** from the left navigation panel. * Select the **Ready to Sign** tab. Every transaction currently waiting for your signature appears here, showing the Transaction ID, transaction type, and Valid Start time. If this tab is empty, you have no pending signing obligations. **Tip:** The **Ready to Sign** tab is your primary action tab. Keep an eye on it whenever you return to the app. *** ### Step 2: Review Transaction Details Before signing, carefully review the full contents of the transaction. You have two entry points. #### Option A — Quick Review from the List From the **Ready to Sign** tab, each transaction row shows the Transaction ID, type, and Valid Start time. For straightforward, low-value transactions you are already familiar with, this summary may be sufficient context before signing. #### Option B — Full Details View (Recommended) For a thorough review — especially for high-value transactions or complex types such as node updates — open the full details view: * Locate the transaction in the **Ready to Sign** tab. * Select **Details** in the Actions column. The details screen displays all transaction parameters, including: | Field | Description | | ----------------------- | -------------------------------------------------------------------------------- | | **Transaction Type** | The type of transaction being executed (e.g., Account Update, Token Transfer). | | **Transaction ID** | The unique identifier for this transaction on the Hedera network. | | **Fee Payer Account** | The account that will be charged the transaction fee. | | **Valid Start** | The date and time when the transaction becomes eligible for network submission. | | **Max Transaction Fee** | The maximum HBAR amount authorized for the transaction fee. | | **Transaction Memo** | Any public memo attached to the transaction (visible on the network ledger). | | **Signatures** | A list of all required signers, showing who has signed and who is still pending. | *** ### Step 3: Sign an Individual Transaction Once you have reviewed the transaction and are ready to proceed, you can sign in one of two ways. #### From the Ready to Sign List * In the **Ready to Sign** tab, locate the transaction. * Select the **Sign** or **Details** action button on the transaction row. * A confirmation summary appears, displaying the transaction type, fee payer account, and maximum fee. * Review the summary carefully — this is your final checkpoint. * Select **Confirm** to apply your signature. #### From the Details View * Open the transaction in the details view as described in Step 2. * Scroll to the bottom of the details screen. * Select **Sign**. * The same confirmation summary appears. * Select **Confirm** to apply your signature. After signing, the transaction moves to the next stage: * If other signers are still required, the transaction moves to the **In Progress** tab. * If your signature was the final one needed, the transaction moves to **Ready for Execution**. *** ### Step 4: Sign Group Transactions #### What Is a Group Transaction? A group transaction bundles multiple individual transactions together for sequential or parallel execution. Group transactions are common where several related operations — such as a batch of token transfers or a series of account updates — must be reviewed and signed together before any of them execute. Each transaction within the group follows the same threshold-signing rules as a standalone transaction. When you open a group transaction's details view, a **signature progress indicator** shows how many of the required signatures have been collected so far, with each member listed alongside their signing status. #### Signing Through a Queue with the Next Button When you have multiple transactions waiting in the **Ready to Sign** tab, the **Next** button lets you move through them efficiently without returning to the list view each time. * Open the first transaction in the **Ready to Sign** tab and select **Details**. * Review the transaction, then select **Sign** and **Confirm**. * Select **Next** — you are taken directly to the details view of the next transaction in your queue. * Repeat until all transactions are signed. The **Next** button disappears when you have reached the last transaction in your queue. That is your signal that your **Ready to Sign** tab is empty. #### Sign All — Signing Your Entire Queue at Once For the fastest workflow, use the **Sign All** button at the top of the **Ready to Sign** tab to sign every transaction in your queue simultaneously. * Select the **Ready to Sign** tab. * Select **Sign All** at the top of the list. * A consolidated batch summary appears, listing every transaction that will be signed. * Review every transaction type and ID in the list carefully. * If everything is correct, select **Confirm**. Your private key signs every transaction in the batch simultaneously. * Each item's status updates in real time as signatures are applied. **Sign All requires careful attention.** You are authorizing every transaction in your queue with your private key, and there is no undo on the Hedera network. If any transaction looks unfamiliar or unexpected, close the dialog and investigate that transaction individually in the details view before using Sign All. *** ### Verifying Your Signature After signing, confirm that your signature was properly recorded using these three checks: **1. Tab movement** — The transaction should no longer appear in your **Ready to Sign** tab. It moves to **In Progress** if other signers are still needed, or to **Ready for Execution** if the full threshold has been met. **2. Signatures section** — Open the transaction details and scroll to the **Signatures** section. Your name or key should appear in green font with a signed status and a timestamp. **3. History tab** — Once the transaction executes, it appears in the **History** tab with a **SUCCESS** status badge, confirming it was accepted by the Hedera network and permanently recorded on the ledger. Based on your settings you will also receive an in-app notification — and optionally an email — confirming successful execution. Clicking that notification takes you directly to the History entry for that transaction. *** *** --- # 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://transactiontool.hedera.com/transactions/signing-transaction-s.md?ask=&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.