> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/cregis-wallet-guide/zh-tw/resources/faq/wallet/shard_authorizing.md).

# 為什麼我想授權分片給成員時成員沒有導入的選項？

如需授權分片給成員，首先要確認錢包創建人已把該員加入錢包，操作入口如下：

<figure><img src="https://3200384756-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPoazW59IJbERNbp3S6uz%2Fuploads%2FSMXiMhpdRXFxeK7cy9R0%2Fimage.png?alt=media&amp;token=6409f80a-bdd9-4773-839e-1661c972bcf5" alt=""><figcaption></figcaption></figure>

如確認已把成員加入錢包，便可以進行授權動作，如創建人沒有完成授權流程，成員是<mark style="color:green;">**不會出現導入的選項**</mark>。詳細授權步驟可參考[這裡](/cregis-wallet-guide/zh-tw/transaction_and_risk-control/shard.md#shou-quan-fen-pian-gei-ling-yi-ge-qian-bao-cheng-yuan)。


---

# 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://support.cregis.com/cregis-wallet-guide/zh-tw/resources/faq/wallet/shard_authorizing.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.
