> For the complete documentation index, see [llms.txt](https://tronpower.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://tronpower.gitbook.io/docs/for-sellers/enable-automation/permission-manual-setup.md).

# Permission (Manual Setup)

{% stepper %}
{% step %}

## **Go to**[ ](https://nile.tronscan.org/#/wallet/account)[**https://tronscan.org/#/wallet/permissions**](https://tronscan.org/#/wallet/permissions)

<figure><img src="/files/rRQrEn0WsYUAWm9z41vB" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Connect your Wallet

<figure><img src="/files/1xL0k10RI7prIlAoYSwB" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Edit Permissions

Click the "**Edit Permission**" button in the Owner Permissions section.

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

{% endstep %}

{% step %}

### Add Active Permission

At the top right of the **Active Permissions** section, click "**Add Active Permission**"

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

{% endstep %}

{% step %}

### Fill in active permission details

* You will now see a popup for "Add Active Permission"

<table><thead><tr><th width="226" valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">In the Permission Name, you can put anything (E.g. Tronpower)<br><br>Click "+Add" button under "Operation(s)" , you will see another popup</td><td><div><figure><img src="/files/W3wdrjvh8nNUChIkoJ0V" alt=""><figcaption></figcaption></figure></div></td></tr><tr><td valign="top"><p>Select the following operations:<br><br><strong>Required</strong></p><ul><li><em>Delegate Resources</em></li><li><em>Reclaim Resources</em></li></ul><p><br><strong>Optional</strong></p><ul><li><em>TRX Stake 2.0</em></li><li><em>TRX Unstake 2.0</em></li><li><em>Vote</em></li><li>Claim Voting Rewards</li></ul><p></p><p>Click <strong>save</strong></p></td><td><div><figure><img src="/files/2NxA9GUovERH5r8xrQZz" alt=""><figcaption></figcaption></figure></div><div><figure><img src="/files/pNdiW1nUfFxO0szB44Mh" alt=""><figcaption></figcaption></figure></div></td></tr><tr><td valign="top"><p>In the Threshold box, enter <strong>1</strong><br><br>In the Authorized To (1/5), <br>Enter <br>[See below for MAINNET / TESTNET Delegator Address]<br><br>and 1 for the weight</p><p></p><p></p><p>Click Add<br><br><br><br><br></p></td><td><div><figure><img src="/files/wHLKQf9tYNxCil7wV9rO" alt=""><figcaption></figcaption></figure></div></td></tr></tbody></table>

{% hint style="success" %}
**Mainnet Delegator Address (Only for mainnet)**\
\
&#x20;TPowCSwSV3bSz9gTNxKCPrFacMxwBpxHTL
{% endhint %}

{% hint style="warning" %}
**Nile Testnet Delegator Address ( Only for testnet playground)**\
\
TCGuvHHReifAE2PwKA7bSwhA6fLm95U6Zf
{% endhint %}

{% hint style="info" %}
The TRON account permission model is part of a multi-signature and permission management design.\
In this case, only one address is given access to these permission and so threshold should be 1 and weight for the address should be 1\
\
Read more at the official tron developer documentation site:\
<https://developers.tron.network/docs/multi-signature>
{% endhint %}

{% hint style="info" %}
Threshold means how much weight of all addresses with their given weights is required in order to execute a transaction in relation to the permissions allowed.\
\
Example 1\
\
Address1 | Weight : 1\
\
Only one address is considered , so threshold is 1 and the signature weight of the address is 1 , so a transaction can be made on behalf of your addresss. (This is required for automated selling)\
\
Example 2\
Address1 | Weight : 1\
Address2 | Weight : 1\
\
If threshold is 2 , it means both addresses must sign a transaction
{% endhint %}

{% hint style="info" %}
\
The signature weight means how much weight is given to the address. If multiple addresses are included in the permission setting, in order to successfully execute the transaction ,  the sum of the weights must equal the threshold .<br>
{% endhint %}
{% endstep %}

{% step %}

### Save active permission by signing transaction

* You should see the active permission added

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

* Click the **Save** button in the ***Owner Permission*** section to complete the multi-sig process.

<figure><img src="/files/8kWbt0JOyBCq9TUX4saR" alt=""><figcaption></figcaption></figure>

* Wait for the transaction to confirm on the blockchain (\~1min) and go back to the "Enable Automatic Selling" section

{% endstep %}

{% step %}

### Manual Permissions complete

Congratulations , you've just configured permissions to our automated selling delegator wallet.

You can now go to back to tronpower to enable automated selling.
{% endstep %}
{% endstepper %}

## **Continue to Automated Selling Process**

Go to **"Step 6) Configure Pool Setting"**

{% content-ref url="/pages/QH5r4AYTEIOMsNUU7xhR" %}
[Setup automated selling](/docs/for-sellers/enable-automation/setup-automated-selling.md)
{% endcontent-ref %}


---

# 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://tronpower.gitbook.io/docs/for-sellers/enable-automation/permission-manual-setup.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.