> 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/web3-defi-and-nft/defi/web3-governance-and-configuration/customize-dapps-catalog-on-evm-accounts.md).

# Customize DApps catalog on EVM accounts

{% hint style="success" %}
This article is for Administrators only.
{% endhint %}

## Overview

With the configurable DApp browser located in each account, administrators can now:

* Customize DApp access by account
* Define advanced Contract Interactions permissions

## Before you begin

In order to be able to use this feature, you will need to have at least one smart-contract enabled EVM account. For more information on how to enable smart contract functionalities on Ethereum accounts, please refer to [this article](/web3-defi-and-nft/defi/deploy-a-smart-contract.md).

## Instructions

1. Go to a smart contract enabled account.
2. In the top navigation bar, select “DApps”
3. You can now toggle (or untoggle) any DApps that you wish to activate on this account (or deactivate). When activated, any Operator in the Creation step of the Smart Contract governance rule will be able to connect this account to the DApp in the DApp catalog. This enables you to segregate and configure your EVM accounts based on their use cases, so that they can only interact with selected DApps and you can in return define the right governance flows. For instance, for a yield-generation oriented account, you can choose to only activate Aave, Alkemi, yearn.finance and Lido.
4. Once you have configured your account’s access as you wish, you can confirm the request.

## Result

A *Create SCI config.* request is submitted for approval to all Administrators in the workspace. They do not need their device to approve the request.

## What's next?

The entity will be created once the request is approved by the number of Administrators defined in the admin rule.


---

# 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/web3-defi-and-nft/defi/web3-governance-and-configuration/customize-dapps-catalog-on-evm-accounts.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.