> For the complete documentation index, see [llms.txt](https://docs.capsulelabs.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.capsulelabs.xyz/capsulenft/overview/capsule-collections/metamaster.md).

# Metamaster

A Metamaster, also known as an Uniform Resource Identifier (URI) Owner, is commonly used by creators to display NFT specific metadata. On creation, a collection can be passed a Metamaster - either a user address or the zero address.

#### If set to a **User Address**:

The user has the ability to change the metadata assigned to any NFT in that collection. 

This option could be very valuable for any collection owner that would want to ensure NFTs within their collection meet certain quality standards, or for NFT collections that require metadata updates after they have been minted. 

The Metamaster can be changed at any point - to learn more, read [Developer - Managing a Capsule Collection](/capsulenft/developer-walkthroughs/developer-managing-a-capsule-collection.md).

#### If set to the **Zero Address**:

The Metamaster can alternatively be set to the zero address in order to prevent anyone from changing NFT metadata in a collection. After setting the Metamaster to the zero address, the metadata and Metamaster can no longer be changed by any user.

{% hint style="info" %}
**Collection *****Metamaster***** vs. Collection *****Owner***

A Metamaster is the controller of all metadata in the Capsule Collection, meaning they have the ability to reassign tokenURI data. 

An Owner is able to lock any Capsule Collections they own. In addition, if a Capsule Collection is private, only the Owner is able to mint to that collection. 

A collection may have one of the following structures:

* User A is Metamaster and Owner.
* User A is Metamaster, and User B is Owner.
* The Metamaster is set to the zero address. User A is Owner.
  {% endhint %}

### Related Tutorials

{% content-ref url="/pages/6GI3x8AzCdRQjo6XPNYH" %}
[Developer - Managing a Capsule Collection](/capsulenft/developer-walkthroughs/developer-managing-a-capsule-collection.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://docs.capsulelabs.xyz/capsulenft/overview/capsule-collections/metamaster.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.