# What permissions does the extension require at installation?

This is the list of requirements required to run the Alby extension:

```json
...
"host_permissions": ["*://*/*"],
"permissions": [
    "identity"
    "nativeMessaging",
    "notifications",
    "scripting",
    "storage",
    "tabs",
    "unlimitedStorage"
]
...
```

**Host Permissions**\
Allows the extension to read information from websites you visit (e.g. meta tags with lightning information) and inject JavaScript to provide websites with APIs such as WebLN, Nostr, webbtc and liquid. 

**Identity**\
Needed to connect to your Alby Account via OAuth2 APIs. 

**Native messaging**\
If you want to connect your own node via TOR this allows the extension to communicate with the Alby Companion App (which connects your browser to the TOR network)

**Notifications**\
Alby notifies you of successful or failed payments through browser notifications.

**Scripting**\
Allows Alby to inject JavaScript into websites to offers APIs for websites to interact with your wallet. 

**Storage**\
Allows the extension to save credentials (always encrypted with your password) and other information (e.g. permissions you gave to certain websites, etc).

**Tabs**\
Allows to get the active tab and fetch payment information provided by websites in their meta tags. 

**Unlimited Storage**\
Storage is usually hard-limited to 10 MB, this is mostly just a preemptive measure for users not to hit this limit. 

<br>


---

# 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://guides.getalby.com/user-guide/browser-extension/faq/what-permissions-does-the-extension-require-at-installation.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.