> For the complete documentation index, see [llms.txt](https://docs.v2.like.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v2.like.co/zh/depub/book-store/authz.md).

# 管理 Authz 授權

容許他人為你傳送 NFT

{% hint style="warning" %}
此文檔只適用於 Liker Land 和 LikeCoin v2。如需了解 [3ook.com](http://3ook.com/) 和 LikeCoin v3，請至 [docs.3ook.com](http://docs.3ook.com/) 及 [dao.like.co](https://dao.like.co/)。
{% endhint %}

到 [Liker Land Book Press](https://publish.liker.land/) 網站，進入網站後點左下角「Sign in」連結錢包，再點「[NFT Authz Grants](https://publish.liker.land/authz)」。

### Send NFT Authz Grants Management Page

授予其他錢包發送 NFT 的授權許可（即 NFT Authz 權限）即容許他們代表你發送你所擁有的任何 NFT，不限於出版的 NFT 書籍或新發行的 Writing NFT。請謹慎使用，並且只授權給你信任的人。

* 在 **Current Grants** 的錢包清單顯示 Wallet 錢包地址及 Expiration 即該錢包的授權到期日。點「**Renew**」可更新授權，點「**Revoke**」即撒消授權。
* 在 **Grant new send NFT Authz** 欄位輸入錢包地址再點「**Submit**」可創建新的授權。

<figure><img src="https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FZRQPZcM7FL6VLMDl9Rrr%2FNFT%20Authz%20Grants.png?alt=media&amp;token=26459ab5-7fd0-473e-802a-7a76caa2fc7b" alt=""><figcaption><p>NFT Authz Grants</p></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.v2.like.co/zh/depub/book-store/authz.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.
