</a>

LNBits Admin UI

We introduced the Admin UI as the new default to make setup simpler and more straightforward. Instead of hand editing the .env file, you configure key server settings directly in the frontend with clear labels and guardrails.

On a fresh install the Admin UI is enabled by default, and at first launch you are prompted to create Super User credentials so that sensitive operations, such as switching funding sources, remain in trusted hands. When the Admin UI is enabled, configuration is written to and read from the database; for all settings managed by the UI, the parameters in .env are largely no longer used. If you disable the Admin UI, the .env file becomes the single source of truth again.

For privileged actions and role details see Super User & User Roles
For a complete reference of legacy variables consult .env.example.

grafik

[!WARNING] Some settings remain .env only. Use .env.example as the authoritative reference for those variables.

What you can do with the Admin UI

Switch funding sources and other server level settings
Manage who can access LNbits (Allowed Users)
Promote or demote Admin Users
Gate extensions to Admins only or disable them globally
Adjust balances with credit or debit
Adjust site customization

[!NOTE] See Super User for the role and permission differences compared to Admin Users.

Enabling or disabling the Admin UI

The Admin UI is enabled by default on new installs. To change the state:

Stop LNbits
```
sudo systemctl stop lnbits.service
```
Edit your .env
```
cd ~/lnbits
sudo nano .env
```

Set one of

# Enable Admin UI
LNBITS_ADMIN_UI=true

# Disable Admin UI
LNBITS_ADMIN_UI=false

Start LNbits
```
sudo systemctl start lnbits.service
```

[!NOTE] With the Admin UI enabled, config is DB-backed and UI-managed settings ignore .env. Disable it to revert to .env as the single source of truth.

Reset to defaults

Using Reset to defaults in the Admin UI wipes stored settings. After a restart, a new Super User is created and the old one is no longer valid.

First run and Super User ID

On first start with the Admin UI enabled you will be prompted to generate a Super User. If you need to read it from disk later:

cat /lnbits/data/.super_user
# example
123de4bfdddddbbeb48c8bc8382fe123

[!WARNING] For security reasons, Super Users and Admin users must authenticate with credentials (username and password).

After login you will see Settings and Users in the sidebar between Wallets and Extensions, plus a role badge in the top left.

grafik

Allowed Users

When set at least one, LNbits becomes private: only the listed users and Admins can access the frontend. Account creation is disabled automatically. You can also disable account creation explicitly.

grafik

[!WARNING] Assign your own account first when enabling Allowed Users to avoid locking yourself out. If you do get locked out, use your Super User to recover access.

Additional Guides

Backend Wallets — Explore options to fund your LNbits instance.
User Roles — Overview of existing roles in LNbits.
Funding sources — What is available and how to configure each.
Install LNBits — Choose your prefared way to install LNBits.

Powered by LNbits

LNbits empowers everyone with modular, open source tools for building Bitcoin based systems — fast, free, and extendable.

If you like this project, send some tip love or visit our Shop