# Best Practices

Configure permissions

Wallets should support the ability to configure connections directly from the wallet service (e.g. Alby Hub allows you to define permissions such read account balance and make payments)

<figure><img src="/files/6WSzIhZL7LrPI183h26Q" alt=""><figcaption><p>Manage access permissions example from Alby Hub</p></figcaption></figure>

### Set budgets

Users are going to link their wallet account to apps to send and receive payments natively in apps. Enabling your users to set budgets creates an efficient safety measure to not overspend.&#x20;

<figure><img src="/files/aj6zngENOfnV77qVWMoB" alt=""><figcaption><p>Manage budgets example from Alby Hub</p></figcaption></figure>

### Unique Keys

Use unique wallet keys for each connection. This keeps your user's activity across different apps completely separate.

### Sub-wallets

Sub-wallets allow your users to completely isolate their activity, so that apps can only see and access data and funds for that specific app.


---

# 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://docs.nwc.dev/bitcoin-lightning-wallets/best-practices.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.