> For the complete documentation index, see [llms.txt](https://metaclav.gitbook.io/product-guide-for-users/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metaclav.gitbook.io/product-guide-for-users/group-1/metaclav-overview.md).

# MetaClav Overview

### Overview

* MetaClav consists of organizations and workspaces (HD wallet)\ <br>

  <figure><img src="/files/Rgj2nx98h40vPCRqe2Mu" alt=""><figcaption></figcaption></figure>
* Workspace at MetaClav is a non-custodial HD wallet based on MPC tech, that enables you to generate as many wallet addresses as you would like to and operate (sign transactions) with those wallet addresses.<br>

  <figure><img src="/files/Zv4T0XRMzz6ah0pbwH7s" alt=""><figcaption></figcaption></figure>
* There are 3 different user roles that can onboard into each organization and workspace as an Admin, Custodian or Signer role.
  * Admin is an organization level role (email that has created the org). Admins can create new workspaces within an organization, as well as manage users for each workspace&#x20;
  * Custodian is a workspace level role. Custodians are the users that are the "owners" of given workspaces and generate the non-custodial MPC key share in MetaClav's iOS app when activating a workspace
  * Signers are custodian's trusted parties that custodians can add as many as they want to, so that these users can sign transactions on custodian's behalf
* Operational Feature for MetaClav are transactions, where these transactions are treated more such as tickets for you or your team to operate on. All transactions have to be signed by a device (iOS) that holds the non-custodial key share. This can be either Custodain's device or Signer's device\ <br>

  <figure><img src="/files/SQ4j4iIpRbWzgwr4n8ou" alt=""><figcaption><p>Custodian or Signer can approve or reject a transaction</p></figcaption></figure>
* There is also backup and emergency recovery of the keys for the customers so that, our customers can take full custody of their crypto assets without asking permission from our platform or company. As service providers our goal is to help our customers to scale operations by adding trusted parties.\ <br>

  <figure><img src="/files/AMbIckrTqpg2trT7ySog" alt=""><figcaption><p>Backup of the workspace root keys , for emergency recovery<br></p></figcaption></figure>

  <figure><img src="/files/Bjl50VVlwrq1AdEjpN7P" alt=""><figcaption><p>Emergency offline recovery of the backup kit</p></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 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://metaclav.gitbook.io/product-guide-for-users/group-1/metaclav-overview.md?ask=<question>&goal=<endgoal>
```

`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.