> For the complete documentation index, see [llms.txt](https://docs.t-rex.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.t-rex.network/guides/issuer.md).

# Issuer

These guides cover what an Issuer does to bring an asset onto the register and to configure it: deploying the suite, wiring its roles, setting who is eligible, setting the rules, and upgrading.

| Order | ID | Guide                                                                                          | What it does                                                                                         |
| ----- | -- | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| 1     | 01 | [Deploy a token suite](/guides/issuer/01.-deploy-a-token-suite.md)                             | Creates the contracts of one asset in one transaction.                                               |
| 2     | 25 | [Commission a suite and grant roles](/guides/issuer/25.-commission-a-suite-and-grant-roles.md) | Makes the suite operable: maps its functions to roles and gives the roles to the Issuer's operators. |
| 3     | 03 | [Configure required claim topics](/guides/issuer/03.-configure-required-claim-topics.md)       | Sets what an investor must prove to hold the asset.                                                  |
| 4     | 04 | [Add a trusted Claim Issuer](/guides/issuer/04.-add-a-trusted-claim-issuer.md)                 | Sets whose attestations count.                                                                       |
| 5     | 20 | [Remove a trusted Claim Issuer](/guides/issuer/20.-remove-a-trusted-claim-issuer.md)           | Stops counting an issuer's attestations.                                                             |
| 6     | 11 | [Add a compliance rule](/guides/issuer/11.-add-a-compliance-rule.md)                           | Binds and configures a compliance module.                                                            |
| 7     | 12 | [Remove a compliance rule](/guides/issuer/12.-remove-a-compliance-rule.md)                     | Unbinds a compliance module.                                                                         |
| 8     | 26 | [Authorize spenders](/guides/issuer/26.-authorize-spenders.md)                                 | Sets which third parties may execute transfers for holders.                                          |
| 9     | 27 | [Upgrade a suite](/guides/issuer/27.-upgrade-a-suite.md)                                       | Moves a suite to a new version.                                                                      |

The "Order" column is the order in which an Issuer usually performs these operations for a new asset. The "ID" column is the permanent reference number of each guide. The two differ because a guide keeps the number it received when it was added to the catalog: commissioning a suite was added with T-REX 5 and is number 25, although it comes second. See [How guides are numbered](/guides/about-the-guides.md).

For a new asset, the usual path is orders 1 to 4, then 6, then the first mint and the lifting of the pause.


---

# 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://docs.t-rex.network/guides/issuer.md?ask=<question>&goal=<user_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.