> For the complete documentation index, see [llms.txt](https://docs.stargate.vechain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stargate.vechain.org/overview/nft-management.md).

# NFT Management

Stargate's NFT management feature enables staking NFT owners to assign limited operational privileges to a **secondary wallet address**—called a **Node Manager**—without compromising ownership or control. This is especially useful for automating certain tasks or integrating with external services, while preserving full authority over staked assets.

A common use case is when a user wishes to entrust actions like **reward claiming** or **app access** (e.g., VeBetterDAO, Discord gated channels) to another address, while retaining full custody of their NFT.

By default, the owner is considered as a manager of its tokens, until another address is set.&#x20;

> 🔁 **Managers are automatically removed** upon any NFT transfer or sale.

***

### Owner Roles and Responsibilities

The NFT owner remains the **sole authority** over the asset. They can appoint or revoke a manager at any time using the Stargate interface—no approval is required from the manager.

Upon assigning a manager, the following controls remain exclusive to the **owner**:

* **Staking or unstaking VET**
* **Locking or unlocking** the NFT for delegation
* **Delegation selection** and exit
* **Transferring, selling, or burning** the NFT
* **Participating in governance**

This ensures that while day-to-day tasks can be outsourced, **strategic and custodial control always remains with the owner**.

***

### Node Manager Capabilities

A Node Manager is assigned unilaterally by the NFT owner—**no transaction is needed** on the manager’s part to accept the role. Managers can:

* **Claim staking rewards** on behalf of the owner
  * All rewards are always sent to the **owner’s wallet**
* Use the NFT for **authentication** or **access control** in third-party apps or integrations (e.g., gated Discord roles, VeBetter endorsements)
* **Remove themselves** as manager at any time through the interface

#### Node Managers Cannot:

* Stake or unstake VET
* Change validator or exit delegation
* Lock or unlock the NFT
* Transfer, sell, or burn the NFT

This strict permission model ensures that managers can **assist** but not **compromise** the NFT's security or financial role.

***

### Use Cases

NFT management is designed to offer **operational flexibility** for:

* Users with **hardware wallets** who wish to avoid frequent signing
* Power users managing **multiple NFTs** across wallets
* DAO participants or services interacting with NFTs for **governance** or **access rights**
* Projects integrating NFTs for ecosystem features that **don’t require staking control**

By separating ownership from limited operational access, Stargate ensures that users can **retain full control** while delegating tasks for convenience and utility.


---

# 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.stargate.vechain.org/overview/nft-management.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.
