> For the complete documentation index, see [llms.txt](https://docs.daimon.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daimon.finance/manager-guide/onboarding-a-castle.md).

# Onboarding a Castle

### 🗺️Overview

To manage a Treasury, asset managing entities create a Management Castle, governed by a MultiSig wallet. There are no limits on how many Treasuries a Management Castle can manage and each manager can be responsible for the administration of one or more Treasuries but all Castles require an initial minimum of three MultiSig members. 

Once the onboarding is complete, the members of the MultiSig become Treasury Managers, and the collective can be added or removed by Trustees to manage their Treasuries. Treasury Managers will then be responsible for the construction of optimal portfolios and the execution of on-chain investments for the given Community Treasury. 

### 👑Powers

Through a system of wallet delegation, the Management Castle MultiSig can opt-in to delegate decisions to a single MultiSig member. The discretionary smart contract-based rulesets of the Treasury Managers, initially hardcoded in the protocol's governing logic, are the following:

* Liquidate Castle
* Add/Remove Manager to MultiSig
* Add/Remove Manager to Treasury
* Delegate/Undelegate Decisions to MultiSig Member