# First login

A new leader creates one administrator on first start. Follow these steps once, after [installing the binary](/docs/install-leader/binary), [running the container](/docs/install-leader/container) or [deploying on Kubernetes](/docs/install-leader/kubernetes).

## Sign in with the printed credentials

1.  Read the startup console of the leader you just started. A fresh account store prints a username and one-time password to the process console (stderr), not the fleet log viewer. Look for output in this form; the values below are placeholders, not credentials you can use:
    
    ```
    smeltr: this leader had no accounts, so one was created.
               username: admin
      one-time password: <generated one-time password>
    It is shown once and is not recoverable. Signing in with it requires choosing a new one.
    ```
    
2.  Open the configured public origin URL in a browser: `http://127.0.0.1:4000` for the local examples.
3.  Sign in with the printed credentials and choose your own password when prompted. Protect any service-console logs containing the temporary password.
4.  Open Admin → Accounts and create named administrators as described in [Accounts and access](/docs/accounts).
5.  For standalone mode, open Status and wait for the automatically enrolled worker in `default` to appear Online. Check that its running commit matches `main`. For a leader-only installation, [enroll a separate worker](/docs/enroll-worker/host) first.