> For the complete documentation index, see [llms.txt](https://guides.getalby.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.getalby.com/user-guide/browser-extension/faq/how-to-access-my-old-account-in-apps-with-the-alby-extension.md).
# How to access my old account in apps with the Alby Extension
The Alby Browser Extension introduced a new way to connect the Alby Account. This greatly improves personalization of the Alby Extension for users of the Alby Account. But it also interferes with the login on other websites. To get access to your original account on other websites, please follow these steps:
**Step 1: Go to** [**https://getalby.com/node**](https://getalby.com/node) **and copy your 'Wallet Connection Credentials'**
**Step 2: In the Alby Browser Extension, click on " + Add " at the end of the extension menu.**
**Step 3: Select 'Connect'**
**Step 4: Select 'Connect'**
**Step 5: Add your Alby Account credentials from Step 1**
**Step 5: Select the Account in the Alby extension via the account selector (top right)**
The account is called LNDHub when you just added it
**You can now log into your previous account on other websites**
####
---
# 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://guides.getalby.com/user-guide/browser-extension/faq/how-to-access-my-old-account-in-apps-with-the-alby-extension.md?ask=&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.
