# Using CoinSign extension to approve dispatch records

1. First, download and install the CoinSign browser extension. Below are the download links for different browsers:\
   Google Chrome – Click [here](https://chromewebstore.google.com/detail/coinsign-extension/ilhkggppoohfhjlnpindnjlbkpenbpkc?hl=en-GB\&utm_source=ext_sidebar) to download the CoinSign extension\
   Mozilla Firefox – Click [here](https://addons.mozilla.org/en-US/firefox/addon/coinsdo-coinsign-extension/?utm_source=addons.mozilla.org\&utm_medium=referral\&utm_content=search) to download the CoinSign extension<br>

2. Before the sub-account user begin to setup the CoinSign browser extension, the main account user must obtain a CoinSign device binding code for that sub-account user via the main account platform. Please follow the steps below:<br>
   1. In CoinSend center, go to the “Sub-account configuration” page and click the “CoinSend” action button next to the desired sub-account user.<br>
   2. In “CoinSend center setting”, navigate to the “Bound CoinSign device” tab and click “Add approval device”. A device binding code for will be generated with a validity period. Share this code with the sub-account user. The sub-account user must complete the CoinSign extension setup within the validity period.<br>

      <figure><img src="/files/0pamT1J9tslhuAAd3Mut" alt=""><figcaption></figcaption></figure>

3. After receiving the device binding code, the sub-account user can begin installing the CoinSign browser extension. Once installed, open the extension and use the top-right menu to change the interface language if needed. After reading the Terms of Use, click “I have read and agree to the terms and conditions”, then click “Proceed”.\
   \
   ![](/files/QlcvSelUNOTQlfJ7gh4Y)<br>

4. On the “Create identity private key” screen, enter the identity private key password twice. After confirming that you have securely backed up this password, click “Create”.\
   \
   ![](/files/82jrXKZvbFBiXsIREmiY)<br>

5. Enter the device binding code obtained from the main account user into the “Device binding code” field, and enter the identity private key password from Step 4. Then click “Confirm”.\
   \
   ![](/files/tQLHl8sLLqbemzv9Qarl)<br>

6. After a successful binding, you will see the "Private key information" screen, indicating that the CoinSign extension has been successfully installed.<br>

   <div align="left"><figure><img src="/files/R0wiDXZo2JAOU5n58Q9T" alt="" width="331"><figcaption></figcaption></figure></div>

7. Whenever a sub-account user needs to use the CoinSign extension to sign an pending dispatch record, click “Plug-in signature” tab in the signature pop-up window and click “Submit.” The browser will automatically launch the CoinSign extension. Enter the identity private key password, then click “Sign” to complete the signing process.<br>

   <figure><img src="/files/5OplZrMKcCbK6Mqk1HW9" alt=""><figcaption></figcaption></figure>

8. If sub-account users wants to delete their CoinSign extension's private key information, open the CoinSign extension, click “Reset identity private key,” enter “DELETE,” and then click “Confirm” to complete the deletion process.<br>

   <figure><img src="/files/JONcKY7z1oJgMe5bagEG" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://coinsdo.gitbook.io/docs/coinsend/how-to/using-coinsign-extension-to-approve-dispatch-records.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
