> 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-enable-alby-only-on-specific-websites.md).

# How to enable Alby only on specific websites?

By default in Chrome browsers extensions are enabled on all websites. But it is possible to enable the Alby extension only on specific websites. Some users prefer this for increased security.

{% hint style="info" %}
**"On click" is not enough.** Alby needs to be able to connect to your lightning account. That's why it can only be **"On specific sites"** or **"On all sites"**
{% endhint %}

**Step 1**: Click on "More Tools" in the browser menu and select "Extensions" or type in chrome://extensions in the browser bar,\
\
**Step 2:** Go to "Details" for Alby

![](https://content.gitbook.com/content/iXQV5vKQhxotviCfaO7L/blobs/7G5hNs5aDpigx2SWlAdB/image.png)

**Step 3**: On the section "Site access" select "On specific sites".

{% hint style="info" %}
If you use the Alby account, you need to enable this by clicking on "Add a new page" and add: **<https://getalby.com>** and **<https://api.getalby.com>** and **<https://ln.getalby.com>**
{% endhint %}

<figure><img src="https://content.gitbook.com/content/iXQV5vKQhxotviCfaO7L/blobs/I0DFWRLxUSMpNM8TSsd8/image.png" alt=""><figcaption></figcaption></figure>

**Step 4:** (optional): If you have your other accounts or nodes connected you have to add those addresses here, too.

**Step 5**: Then visit the page you want to use Alby and click on the Alby icon and enable Alby.

![](https://content.gitbook.com/content/iXQV5vKQhxotviCfaO7L/blobs/W822dx2vtd6O1GG8eHuv/image.png)

**Success!** Have a look at the [Alby app directory](https://getalby.com/discover) to discover new apps to use Alby.


---

# 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-enable-alby-only-on-specific-websites.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.