> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/guides/connectivity-hub.md).

# Connectivity Hub

How to connect a Ledger Enterprise Account to a dapp with WalletConnect, under your normal governance.

**Role: Operators.**

The Connectivity Hub connects your Accounts to dapps. Your assets stay in the Account. Your governance still applies.

The Hub provides access to **WalletConnect**. WalletConnect is an open protocol that links an Account to a dapp, either by scanning a QR code or through a link.

> **Note:** WalletConnect is the only connection method in the Hub today. It works with **Ethereum** Accounts.

## What a dapp can ask for

Once connected, a dapp can ask your Account to do two things:

<table><thead><tr><th width="183.42578125">Request</th><th>What it means</th></tr></thead><tbody><tr><td><strong>Contract interaction</strong></td><td>The dapp asks your Account to call a smart contract</td></tr><tr><td><strong>Sign message</strong></td><td>The dapp asks you to sign a message, which moves no funds</td></tr></tbody></table>

Both become **Requests**. Each one needs the approvals your Account's Rules demand. Each one is signed with your own key.

> **Important:** An Administrator must add a Rule for these operations first. A Rule that lets you send from an Account does not let you interact with contracts. See [**Creating and editing Accounts**](/help-center-v2/guides/accounts/creating-and-editing-accounts.md).

## Connect to a dapp

1. Open **Connectivity Hub**.
2. Open **WalletConnect**.
3. In the dapp you want to use, choose to connect a wallet, then choose WalletConnect.
4. Pair the two by using the connection link.
5. Select the Account to connect.

If the Hub is empty, you have no Account on a supported network. Ask your Workspace Administrator.

## Approve a Request from a dapp

Review every Request before you approve it:

1. **Check the matching Rule.** The Request names the Rule that applies. That tells you who else must approve.
2. **Check the amount and the fee.** The Account must hold enough for both.
3. **Review on your device**, as you would for a transfer.

### Plan for the time it takes

This is the part that catches people out.

A dapp expects a signature quickly. Your governance may need several approvals from several people. If your other Approvers are not ready, the dapp's session can time out before the Request is approved.

The platform warns you when a Request needs more than one approval.

> **Important:** A session that times out during approval cannot be resumed. You start again in the dapp.
>
> If this happens often, ask an Administrator whether contract interaction needs a different approval chain from the one used for large transfers.

## If something does not work

<table><thead><tr><th width="272.73828125">What you see</th><th>What it means</th></tr></thead><tbody><tr><td>No matching rule found</td><td>No Rule covers this operation for this amount or destination. Ask an Administrator</td></tr><tr><td>Cannot determine matching Rule</td><td>The platform could not resolve which Rule applies. Contact support</td></tr><tr><td>Insufficient balance</td><td>The amount plus the maximum fee is more than the Account's available balance</td></tr><tr><td>No available app yet</td><td>You have no Account on a supported network. Ask your Administrator</td></tr></tbody></table>

> **Warning:** A connected dapp can ask your Account to sign anything its Rules allow. Connect only to dapps you trust, and read the operation on your device before you approve it. See [**The security model**](/help-center-v2/concepts/the-security-model.md).

## Related

* [**How governance works**](/help-center-v2/concepts/how-governance-works.md)
* [**Ethereum and EVM networks**](/help-center-v2/reference/networks/ethereum.md)
* [**The security model**](/help-center-v2/concepts/the-security-model.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 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://help.enterprise.ledger.com/help-center-v2/guides/connectivity-hub.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.