> For the complete documentation index, see [llms.txt](https://docs.vultisig.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vultisig.com/app-guide/vault-management/vault-reshare.md).
# Vault Reshare
{% hint style="danger" %}
**Advanced feature.** Access to funds is at risk if not properly managed.
{% endhint %}
Reshare in settings
***
## What is Resharing?
Resharing modifies the number of devices in a vault without changing wallet addresses or moving funds. This feature enables:
* Adding new devices to increase security
* Removing devices that are no longer needed
* Including Vultiserver in an existing Secure Vault
* Replacing a lost device with a new one
***
## Requirements
{% hint style="info" %}
A threshold majority is **always** required. For a 2-of-3 vault, at least 2 devices must be present.
{% endhint %}
***
## Video Guides
**Resharing from 3-of-4 to 2-of-3:**
[](https://x.com/iceman00008/status/1958446928271900905/video/1)
**Resharing from 2-of-2 to 2-of-3:**
[](https://twitter.com/iceman00008/status/1825339005673857356/video/1)
***
## How to Reshare
1. Go to **Settings** → **Vault Settings** → **Reshare**
2. Choose whether to include Vultiserver
3. Start the reshare ceremony on the initiating device
4. Join with other devices (scan QR or use relay)
5. Add new devices or exclude devices as needed
6. Complete the keygen process
***
## Use Cases
### Adding Devices
Join additional devices during the reshare ceremony to increase security:
* 2-of-2 → 2-of-3 (adds backup device)
* 2-of-3 → 3-of-4 (increases threshold)
### Removing Devices
Exclude a device by not joining it in the ceremony:
* 3-of-4 → 2-of-3 (reduces complexity)
* Remove a compromised device
### Replacing Lost Devices
If a device is lost but you have threshold access:
1. Initiate reshare with remaining devices
2. Add the replacement device
3. Complete reshare to issue new shares
***
## Critical Warnings
{% hint style="danger" %}
**Backup immediately after resharing!**
After resharing, all vault shares change. Old backups are NOT compatible with new shares.
{% endhint %}
{% hint style="info" %}
Old vault shares can still sign with each other. Resharing does not invalidate the old set—it creates a new parallel set.
{% endhint %}
***
## Related
* [Vault Backup](/app-guide/vault-management/vault-backup.md) - Essential after resharing
* [Vault Upgrade](/app-guide/vault-management/vault-upgrade.md) - Change TSS protocol
---
# 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.vultisig.com/app-guide/vault-management/vault-reshare.md?ask=&goal=
```
`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.