# Admin Components Diagram

<figure><img src="/files/wUEx6xHgEOPVL622nYMC" alt=""><figcaption></figcaption></figure>

This diagram focuses on the regular user role and its interactions within the system. Here's a breakdown of the diagram:

1. Main Components:
   * Registry: Provides access to other components and configurations.
   * InterNetworkExecutor: Handles cross-network swaps.
   * IntraNetworkExecutor: Handles within-network swaps.
   * Vault: Manages token deposits and withdrawals.
   * RegularUser: Represents the external entity with the regular user role.
2. Relationships:
   * Solid lines with open arrows (-->) represent dependencies or usage.
3. Entry Points:
   * InterNetworkExecutor: The `swap(InterNetworkSwapActions)` method is an entry point for cross-network swaps.
   * IntraNetworkExecutor: The `swap(SwapAction)` method is an entry point for within-network swaps.
   * Vault: The `deposit(uint256)` and `withdraw(uint256)` methods are entry points for vault operations.
4. Key Interactions:
   * The RegularUser interacts directly with InterNetworkExecutor, IntraNetworkExecutor, and Vault.
   * All components depend on the Registry for accessing other parts of the system.

<details>

<summary>Diagram code</summary>

```mermaid
classDiagram
    class Registry {
        +setRolesManager()
        +setFeesReceiver()
        +setInterNetworkExecutor()
        +setIntraNetworkExecutor()
        +setCentralGateway()
        +setVaultToken()
        +setProtocolFee()
        +setVaultFee()
        +setSpecificGateway()
        +setTokensReceiver()
    }

    class RolesManager {
        +grantOperator()
        +revokeOperator()
    }

    class Gateway {
        +setMessagingProtocolGateways()
    }

    class Admin["Admin (External)"]

    Admin --> Registry : calls
    Admin --> RolesManager : calls
    Admin --> Gateway : calls

    Registry --> RolesManager : uses

    class Registry {
        <<entrypoint>>
    }
    class RolesManager {
        <<entrypoint>>
    }
    class Gateway {
        <<entrypoint>>
    }


```

</details>


---

# Agent Instructions: 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:

```
GET https://docs.1layer.io/readme/architechture/smart-contracts/admin-components-diagram.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.