> For the complete documentation index, see [llms.txt](https://coinsdo.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coinsdo.gitbook.io/docs/coinsend/how-to/set-up-server-role-and-server-account.md).
# Set up server role and server account
{% hint style="info" %}
**Functional Overview:** CoinSend's automatic withdrawal can only be submitted and approved by server-side accounts. Therefore, a server account must be created before using the automatic withdrawal feature.
{% endhint %}
1. Log in to the main account dashboard and go to the “Role management” page. Click “Add role”, then enter the role name in the “Add role” window, select “Server account Role” as the role type, and fill in the remarks field (optional). Finally, click “Submit” to complete the creation of the server account role.
2. Click the “CoinSend” Action of the server account role, then select “Yes” under “Data submission permission” to authorize the role to submit dispatch records. After clicking “Submit”, enter the **main account’s Google verification code** to apply the changes.
3. On the “Sub-Account” page, click the “Add sub-account”.
4. Enter the sub-account name and select “Server account” as the Account Type, and choose the required role. Then click “Submit” to complete the setup.\
**Note: Provide the server account name to your technical team so they may include it in the "submitAccount" parameter required for automatic withdrawal.**
5. On the “Sub-Account” page, click the “CoinSend” action button of the server account to enter the “Bound Coinsign device” page. Click "Add approval device" then the device name, public key of the device and **main account’s Google Authenticator code**.
Then click “Submit” to complete the update.\
**Note: Please have your technical team generate an RSA public/private key pair. Enter the public key on the “Add approval device” page, and use the private key for signing automatic withdrawals.**
\
**Note: When entering the public key, remove the “BEGIN” and “END” lines and provide only the key content. Ensure there are no spaces or line breaks (see example below) to avoid verification failures due to incorrect formatting.**
6. After adding the approval device for the server account, **provide its device UUID to your technical team so they may include it in the reviewUuid and approveUuid parameters required for automatic withdrawals.**
7. This step will grant the server account data approval (first-level approval) and execution approval (second-level approval) permissions.
In the CoinSend dashboard, go to the “CoinSend client” page and click the “Authorize” action button for the desired client. Add the server account under both “Data approval” and “Execution approval,” then click “Submit.” Complete the authorization by scanning the QR code with the CoinSign app or signing via the CoinSign browser extension (you will need to enter the **CoinSend client password** and **CoinSend Google Authenticator code**).
