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

# Connect

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

**Role: Operators.**

**Connect** links your Accounts to dapps. Your assets stay in the Account. Your governance still applies.

**Connect** 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 **Connect**. 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:** A Master 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**](https://help.enterprise.ledger.com/help-center-v2/guides/accounts/creating-and-editing-accounts.md).

## How a dapp transaction is governed

The platform creates every transaction that a dapp asks for as a contract interaction, whatever the transaction does.

* **The Contract Interaction Rule decides.** Its amount threshold applies to the native value that the transaction sends. Its Smart Contract Whitelists apply to the address that the transaction calls. Send Rules never apply to a dapp transaction.
* **Transaction Check screens it.** The result shows before you review. If you select **Cancel** on a Transaction Check dialog, the dapp call ends and no Request is created. See [**Transaction Check**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/sending-assets.md#transaction-check).
* **Clear Signing applies as for any contract interaction.** A call that Clear Signing does not cover is blind signed. See [**Contract operations**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/contract-operations.md).

## Connect to a dapp

1. Open **Connect**.
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 **Connect** shows **No dapps available**, you have no eligible Account. An eligible Account is an Account on Ethereum or on an EVM network, with a Rule that lets you interact with contracts or sign messages. An Account on a deprecated network is not eligible. Ask a Master Administrator for access to one.

WalletConnect shows the dapp only the eligible Accounts on Ethereum and on the Sepolia testnet.

## 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. **Check the Transaction Check result.** A flagged or unverified result needs your acknowledgement.
4. **Review on your device**, as you would for a transfer.

### While the Request collects approvals

The dapp waits for the result until the Request executes. While other Approvers review the Request, the dialog shows "Waiting for additional approvals…". Then it shows "Executing Request…". When the Request executes, the dapp receives the transaction hash.

If you close the dialog before the Request executes, the dapp receives a failure. Closing the dialog does not cancel the Request.

### Plan for the time it takes

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. The warning, **Potential session timeout**, opens before the review. Select **Proceed** to continue.

> **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>On a Sign message Request: no Rule covers this message. Ask a Master Administrator</td></tr><tr><td>No matching Rule found for the given amount and recipient</td><td>On a Contract interaction Request: no Rule covers this amount and recipient. Ask a Master Administrator</td></tr><tr><td>Cannot determine the matching Rule</td><td>The platform could not resolve which Rule applies. Contact support</td></tr><tr><td>No permission to sign</td><td>You have no Rule that lets you sign messages from dapps on this Account. Ask a Master Administrator</td></tr><tr><td>No permission to execute</td><td>You have no Rule that lets you execute contract interactions from dapps on this Account. Ask a Master Administrator</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 dapps available</td><td>You have no eligible Account. Ask a Master 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**](https://help.enterprise.ledger.com/help-center-v2/concepts/the-security-model.md).

## Related

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.enterprise.ledger.com/help-center-v2/guides/connectivity-hub.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.
