# Navigating during the transition

{% hint style="info" %}
While Webapp 2.0 is rolling out, your workspace runs across **two interfaces at the same time**: the new Webapp 2.0 and the legacy interface. This is expected, and temporary. This page explains how to tell which interface to use, and what to expect from accounts that have already moved.

**Note:** The single most useful habit during the transition is this: when an action isn't where you expect it, check the **other** interface before assuming something is wrong.
{% endhint %}

## A note on the rollout

Webapp 2.0 is being introduced progressively, reaching **Operators first** and **Administrators** in a later phase, and expanding network by network. While that's in progress, some actions live in Webapp 2.0 and others remain in the legacy interface. If you're not sure where something is, read this first:

[**Navigating during the transition**](/helpcenter2/getting-started/navigating-during-the-transition.md)

## Which interface do I use?

The rollout reaches Operators before Administrators, and advances network by network, so the right interface depends on **what** you're doing and **which network** you're using.

* **Operator actions on a supported network**: finding accounts, checking balances, reviewing history, sending, receiving, and (where supported) staking are done in **Webapp 2.0**.
* **Administrative actions**: creating accounts and managing users, groups and governance are generally still done in the **legacy interface** during this phase, unless a guide here says a specific action has moved.
* **Networks not yet supported** in Webapp 2.0 continue to be managed entirely in the **legacy interface** for now.

## How migrated accounts behave

As accounts move to Webapp 2.0, you may see the same account referenced from both interfaces. To avoid acting on an account in two places:

* A **migrated account** is the one you act on in **Webapp 2.0**, which is where you send, receive, and see its current balance and history.
* The same account may still be **visible in the legacy interface but not actionable** there, with an indication that it has moved.

## Where are my requests and approvals?

Requests can originate in either interface. If you're expecting something to approve and don't see it, check **Webapp 2.0** first for supported-network actions, then the **legacy interface** for administrative actions and unsupported networks.

## Frequently asked

<details>

<summary>Do I need to do anything to migrate my accounts?</summary>

No. Migration is managed centrally and rolls out by network; you don't trigger it yourself.

</details>

<details>

<summary>Will my keys, devices, or governance change?</summary>

No. Webapp 2.0 is a new interface over the same security model. Your Physical Security Devices (PSDs) and approval rules keep working as before.

</details>

<details>

<summary>An account disappeared from the legacy interface. Is that a problem?</summary>

Usually not. It most likely moved to Webapp 2.0. Look for it there before raising a ticket.

</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://help.enterprise.ledger.com/helpcenter2/getting-started/navigating-during-the-transition.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.