> ## Documentation Index
> Fetch the complete documentation index at: https://docs.groundtech.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage gVault access

> Authorize, verify, and remove an address for direct deposits into a gVault.

The gVault allowlist applies to direct access to an existing gVault. The subject
is an EVM `address`, not necessarily a wallet: it can be an EOA, multisig, smart
account, or another contract.

## Add an address

Call from your backend with the `id` returned by the gVault catalogue:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl -X PUT \
  https://sandbox.groundtech.co/v2/gvaults/ground-ustb-vault/allowlist/0x3Bf25A73a1f1033C2d50Ac65f3C9d6A44123DB81 \
  -H "Authorization: Bearer $GROUND_API_KEY"
```

The operation is idempotent for the desired allowlisted state:

* `200` with `status: confirmed` means no further state change is pending.
* `202` with `status: submitted` and `transactionHash` means Ground broadcast
  the update, but it has not necessarily confirmed.

## Verify the effective state

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl \
  "https://sandbox.groundtech.co/v2/gvaults/ground-ustb-vault/allowlist/0x3Bf25A73a1f1033C2d50Ac65f3C9d6A44123DB81" \
  -H "Authorization: Bearer $GROUND_API_KEY"
```

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "allowed": true
}
```

Do not enable deposits until `allowed` is `true`. A transaction hash proves
submission, not confirmation or effective authorization.

## Remove an address

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl -X DELETE \
  "https://sandbox.groundtech.co/v2/gvaults/ground-ustb-vault/allowlist/0x3Bf25A73a1f1033C2d50Ac65f3C9d6A44123DB81" \
  -H "Authorization: Bearer $GROUND_API_KEY"
```

Removing your organization's grant blocks future deposits after the effective
allowlist state becomes false. It does not seize shares or block redemption of
an existing position. If another authorized organization still grants access,
the effective state may remain true.

## Handle failures

Treat `404` as an unknown gVault or unavailable organization resource, `409` as
a conflicting in-flight state change, and `503` as a temporary submission
failure. Before retrying an uncertain request, read the effective state.

API reference:
[add](/api-reference/add-gvault-allowlist),
[get](/api-reference/get-gvault-allowlist), and
[remove](/api-reference/delete-gvault-allowlist).