What's already configured
The one-click deployment installs Vaultwarden inside a Docker container using SQLite as the default database — no separate database server to set up. The container is bound to your domain with a reverse proxy and TLS certificate already in place, and it's configured to restart automatically if the server reboots.
First login
Open your assigned domain in a browser to reach the Vaultwarden web vault. By default, Vaultwarden allows anonymous account registration, so the first thing to do is create your own account directly from that screen. The admin panel lives at the /admin path of your domain and is protected separately by the ADMIN_TOKEN generated during install — use it to disable further public sign-ups once your account exists, which closes off the most common misconfiguration on a freshly deployed vault.
A few practical notes
Vaultwarden speaks the same API as Bitwarden, so any of the official Bitwarden browser extensions, mobile or desktop apps will connect once you point them at your domain instead of bitwarden.com. If you expect a larger team, PostgreSQL can replace SQLite, but that migration involves exporting existing data first.