> For the complete documentation index, see [llms.txt](https://docs.shardspace.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shardspace.app/developer/how-to-create-a-token/advanced-token-creator.md).

# Advanced Token Creator

Note: For a limited time the Advanced Token Creator is in a FREE beta access. Once the beta period is over the fee to create a token using the Advanced creator will be 250 XRD.

The following behaviours can be set

* Mintable - additional tokens can be minted after the initial token supply has been set
* Burnable - the overall supply of tokens can be reduced from the initial token supply
* Freezable - tokens can be frozen in an account
* Recallable - tokens can be recalled from an account
* Withdrawable - tokens can be withdrawn from an account
* Depositable - tokens can be deposited to an account
* Divisibility - the number of decimals a token can be divided by. Default = 18

## How to create a token using the Advanced creator

1. Select the owning account where the tokens will be deposited
2. Choose a badge that can be used to manage the token and change certain behaviours and settings. Creating a badge is optional.

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

3. Set the token details

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

4. **Assign Rules - Token Permissions**

This is where the behaviour or permissions can be set and who can change them.

* Allow all - Any one has permission to this access behaviour
* Deny all - No one has permission to access this behaviour
* Owner badge - only the holder of a specific badge (resource) has permission to access this behaviour

<figure><img src="/files/2wR6xcvsa1q4NNlhse5M" alt=""><figcaption></figcaption></figure>

4. **Assign Rules - Admin Permissions**

Once a certain behaviour is set there is another layer of configurable administration that if allowed means a Token Permission can be changed later. Again the three main options here are

* Allow all - Any one has permission to change this behaviour at a later time
* Deny all - No one has permission to change this behaviour at a later time
* Owner badge - only the holder of a specific badge (resource) has permission to change this behaviour later

For example a token could be configured with the following settings;

**Token Permission** - **Mintable.** Yes, but only by the holder of the badge specified can mint more tokens.

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

**Admin Permissions** - **Mintable.** Yes, but only the owner of the badge can change the token behaviour from being mintable to not being mintable.

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

5. Changing the Metadata

The final option is whether the token's metadata like name or logo can be updated and whether changing the metadata can be locked forever so no further changes can be made.&#x20;

### Metadata token permissions

Can the tokens metadata be updated and can it be locked

* Allow all - Anyone can update the metadata
* Deny all - No-one can update the metadata
* Owner badge - Only the holder of the badge can update the metadata

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

### Metadata admin permissions

Can the ability to update the token metadata and lock the metadata change

* Allow all - Anyone can update the ability to change or lock the metadata
* Deny all - No-one can update the ability to change or lock the metadata
* Owner badge - Only the holder of the badge can update the ability to change or lock the metadata

<figure><img src="/files/2VxhClVToYVt65LlNgCq" alt=""><figcaption></figcaption></figure>


---

# 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://docs.shardspace.app/developer/how-to-create-a-token/advanced-token-creator.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.