# Controller management

If you want to limit the access to your assets to specific wallets, you can issue the exclusive rights to buy, sell, trade etc. by using a controller. 

{% hint style="info" %}
Adding controller to the asset can only be done by the issuer of an asset
{% endhint %}

You can always check available controllers in "Settings" -> "Controllers". Please, pay attention to the status of your controllers. You can use only "Active" ones. 

* Active - controllers which are written to blockchain
* Updating - controllers which are in the process of writing to blockchain
* Draft - controllers which were created in WLM but not written to blockchain (most likely you didn't sign the transaction)

![](/files/mg1pIO6PB7Lgxx8LvAHl)

First make sure that all the public addresses of the wallets you want to give access to your assets or restrict access are either in My wallets or in Other wallets [Wallet management in WLM + TX.Mobile](/white-label-management-tool/user-guide/wallet-management-in-wlm-+-tx.mobile.md)

## Create new controller

To add a controller, click on “Settings” and choose “Controllers”. Afterwards you can click on “Add controller”. A new form with the option to add an “External controller” or create a “New controller” opens. If you click on “New controller” you can provide a name and a description for it.

![](/files/zhDRPLQq21Vv9Ir9lJXb)

Afterwards, you get a notification and a transaction in TX.Mobile for creating a controller which needs to be signed [Sign and check executed transactions](/white-label-management-tool/user-guide/sign-and-check-executed-transactions.md)

{% hint style="info" %}
Please, note that WLM always uses your Current wallet for creating transaction. Signature will be expected from this wallet. Current wallet is displayed right under your account name in the sidebar menu.
{% endhint %}

After you confirmed the transaction with TX.Mobile, a new controller is created.

## Manage whitelist and blacklist of a Controller

If you select your created controller and click on “Manage”, you can create a “**Whitelist**” and thus give access to your assets to selected wallets or "**Blacklist**" and thus restrict the access to your assets for selected wallets. 

Select the wallets you added previously, to put them on desired type of the list. Finish the process by clicking on “Save” and sign the transaction with TX.Mobile [Sign and check executed transactions](/white-label-management-tool/user-guide/sign-and-check-executed-transactions.md)

![](/files/0rMY8rvzlpORUiayqj3Q)

After you created a controller and added necessary wallets to Whitelist or Blacklist, you can add the controller to an asset you issued.

{% hint style="info" %}
Please, be careful with adding wallets to Whitelist or Blacklist. It doesn't make much sense in having both for one asset.

Only wallets added to Whitelist will be able to receive units of the assets to which the controller will be added..

Only wallets added to Blacklist won't have possibility to receive units of the assets to which the controller will be added. 
{% endhint %}

### Add controller to the asset

Go to “Assets” and select “My Assets”, then choose the asset which you want to add the controller to. On the top right of the page, you now see “Controller”. 

When you click on “Change” you can add the controller to the asset. Only active controllers can be selected. Click on “Select” and confirm with TX.Mobile [Sign and check executed transactions](/white-label-management-tool/user-guide/sign-and-check-executed-transactions.md)

![](/files/fQLqfP3WKAhHEVPOvq85)

The access to the asset is now limited according to Whitelist and Blacklist of your controller.


---

# 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://teos-docs.coreledger.net/white-label-management-tool/user-guide/controller-management.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.