> For the complete documentation index, see [llms.txt](https://docs.tesseract.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tesseract.fi/dedicated-client-vaults/roles-and-access.md).

# Roles & Access

Access to Dedicated Client Vaults is split into two layers: what your **team can do in the Tesseract dashboard**, and who can **move funds on-chain**. They are deliberately separate — no dashboard role can move funds.

### Dashboard roles

When your organisation is onboarded you can invite team members and assign each a role. Roles are ready-made permission sets (individual permissions can also be fine-tuned per user):

| Role                     | What it can do                                                                                                         |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| **Viewer**               | Read-only across the dashboard — clients, KYC status, wallets, vaults and reports.                                     |
| **Whitelisting Manager** | Everything a Viewer can, **plus verify and whitelist wallets** for on-chain access.                                    |
| **Admin**                | Full access, including managing team members (inviting, suspending, adjusting permissions). Provisioned at onboarding. |

### It all ends at wallet whitelisting

The most any dashboard role can do to affect on-chain activity is **whitelist a wallet** — the job of the Whitelisting Manager. Whitelisting only approves a wallet to interact with vaults; it moves no funds.

**Deposits and withdrawals are authorised solely by the whitelisted wallet itself** — no dashboard role, and no one else, can move funds on your behalf. Tesseract's discretionary management rebalances within your chosen strategy under separate, tightly scoped controls and can **never** withdraw to an external address; funds only ever move back to your own whitelisted wallet.

### Recommended: whitelist an MPC wallet or a multisig

Because on-chain control comes down to one wallet, the security of your vault funds is the security of the wallet you whitelist. We recommend whitelisting a wallet that already carries your organisation's custody and approval controls — an **MPC wallet** (e.g. Fireblocks) or an **on-chain multisig / smart account** (e.g. Safe) — so vault interaction reuses your existing security practices (multiple approvers, signing thresholds, transaction policies, audit trails) with no separate approval layer to maintain.

***

See also: [Prerequisites: KYC & Whitelisting](/dedicated-client-vaults/integration-guide/scenario-a/prerequisites.md) · [FAQ](/dedicated-client-vaults/faq.md).


---

# 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://docs.tesseract.fi/dedicated-client-vaults/roles-and-access.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.