> 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/why_cant_i_see_the_team_wallet.md).

# 為什麼我看不到團隊的錢包？

錢包有另外獨立的權限管理，如沒有加入成為錢包成員是不可以看到錢包的。錢包創建人可以根據以下操作找到錢包權限的相關設定：

選擇錢包從在設定找到錢包成員的入口

<figure><img src="https://3200384756-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPoazW59IJbERNbp3S6uz%2Fuploads%2FTvuZUWmbbwD1N4ddAbZf%2Fimage.png?alt=media&amp;token=1d7309e0-18ab-44cb-991a-6c28f89d94fd" alt=""><figcaption></figcaption></figure>

這裡可進行添加或移除錢包成員，同時可進行編輯。

<figure><img src="https://3200384756-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPoazW59IJbERNbp3S6uz%2Fuploads%2Fj1pw7682PVuWFwYsgkiS%2Fimage.png?alt=media&amp;token=1a536b86-51a6-4f4d-835d-9ae771bfe5f6" alt=""><figcaption></figcaption></figure>

以下為錢包中可編輯的權限：

<figure><img src="https://3200384756-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPoazW59IJbERNbp3S6uz%2Fuploads%2F1uuIql2wXLIO64zoRGmg%2Fimage.png?alt=media&amp;token=51af8623-eebc-4ad1-8888-bcedac7dc32a" 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 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/why_cant_i_see_the_team_wallet.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.