> 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/6.-resources-documentation-and-terms/faq/team-account-management/how-to-handle-shards-when-a-member-leaves-the-team.md).

# How to Handle Shards When a Member Leaves the Team?

If the departing member is the wallet creator, it is recommended to replace the wallet for asset management. During wallet creation, Cregis displays the recovery phrase once, which poses a risk of phrase leakage.

If the departing member is not the wallet creator and their shard was authorized to them, the following steps can ensure asset security:

1. **Remove Shards from Specific Devices**\
   Use the wallet's shard management feature to delete all device shards associated with the departing member. This ensures the shards are not exposed.

   <figure><img src="https://3263384427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3NzJ0yGNKhTsgI2zNjK%2Fuploads%2FvQPuydOrht1jiW1gQLsF%2Fimage.png?alt=media&amp;token=e91eab2e-a4ed-402b-9014-b48db947a0a8" alt=""><figcaption></figcaption></figure>
2. **Reset Shards**\
   Resetting wallet shards is another option. However, this will require all shard holders of the wallet to be reauthorized, and it involves the use of the recovery phrase, making it a less optimal solution.\
   Only the wallet creator has the authority to reset shards. The entry point for this operation is shown below:<br>

   <figure><img src="https://3263384427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3NzJ0yGNKhTsgI2zNjK%2Fuploads%2F6bLLiFREDtH0Dw58mt8v%2Fimage.png?alt=media&amp;token=38aa9ba8-aa71-4c24-ad82-3367c249389e" alt=""><figcaption></figcaption></figure>

   Resetting shards requires entering the recovery phrase. Once completed, all related shards of the wallet will be invalidated and must be reauthorized.<br>

   <figure><img src="https://3263384427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3NzJ0yGNKhTsgI2zNjK%2Fuploads%2FoTUCTyVukFSbSlzSGqAM%2Fimage.png?alt=media&amp;token=a8eee947-5bc6-4aca-b79c-7acaa328e92f" 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/6.-resources-documentation-and-terms/faq/team-account-management/how-to-handle-shards-when-a-member-leaves-the-team.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.