> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/platform-guide/accounts/import.md).

# Import a smart account

Add a Bloxchain smart account you already control to the Accounts list on this device.

**Where:** **Accounts → Import** · **You need:** the account's network and contract address; a wallet only if you want to act

<figure><img src="https://2633730519-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GcVTQuj6X0G3RZ3YY7r%2Fuploads%2Fgit-blob-4a921115f6463992b683494554ed223fc26fe937%2F06-import-account.png?alt=media" alt="Import Smart Account dialog with Network, Account name and Contract address fields" width="1000"><figcaption><p>Importing needs only the network and the contract address. It adds an existing account to this browser; it does not grant you any role on it.</p></figcaption></figure>

## Steps

1. On **Accounts**, click **Import**.
2. Choose the **Network**. The helper reads "The network this smart account is deployed on."
3. Enter an **Account name** (optional), for example "Primary Treasury". It is stored on this device only.
4. Paste the **Contract address** (0x…).
5. Click **Import**.

## Validation

| Message                                            | Fix                                                                                             |
| -------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| "Enter a valid 0x-prefixed contract address."      | Check the address. It must be a full 40-hex-character address with the 0x prefix.               |
| "Choose a network."                                | Select the chain the account is deployed on.                                                    |
| "Connect to a supported network before importing." | Your wallet is on a chain the Platform does not know. Switch it or add the network in Settings. |

## What import does

Import writes one entry to the account list stored in this browser (or in your organization's shared list). Nothing happens on-chain. No transaction, no signature and no gas.

The Platform then reads the contract: owner, recovery, time lock, broadcasters, roles, actions and balances. If the address is not a Bloxchain account on that network, the pages will show empty or unreadable data.

## Read-only vs acting

You can import and open any account without a wallet. Balances, roles, approvals and history all load. To act (start a request, approve, execute or change policy) connect a wallet whose address holds a role on that account. Check [My access](/platform-guide/operate/my-access.md) after importing.

## Re-importing

If the address is already on this device, the toast reads "Already on this device — opening it." and the existing entry opens. Otherwise you see "Smart account imported" and the account opens.

## Related

* [Deploy a smart account](/platform-guide/accounts/deploy.md)
* [Open and share an account](/platform-guide/accounts/open-and-share.md)
* [Connect a wallet](/platform-guide/connect-wallet.md)
* [Backup and restore](/platform-guide/settings/backup.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://docs.bloxchain.app/platform-guide/accounts/import.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.