---
id: first-login
title: First login
sidebar_label: First login
---

A fresh install has no users and no instance. The first visit creates both.

## 1. Bootstrap

Open the control plane in a browser. Because no user exists, you land on
`/setup`.

Fill in:

| Field         | Notes                                 |
| ------------- | ------------------------------------- |
| Instance name | Display name. Shown throughout the UI |
| Email         | Becomes your sign-in identity         |
| Password      | Stored bcrypt-hashed                  |

Submitting creates the instance and its **owner** you.

:::warning Bootstrap works exactly once
The endpoint is open only while the database has no users. As soon as the first
one exists, There is no second chance to create the first owner, so record the
credentials before you continue.
:::

## 2. Copy the Instance ID

Once you have finished setup you will see the successfully created page.

This will show the Instance ID. You will need this ID when creating a license in the HQ.

## 3. Sign in

Click the continue to sign in button on the successful setup page.

You will be taken to `/login`. Sign in with the email and password you just set.

## 4. Look around

You land on the servers dashboard, which is empty. The sidebar is the whole
product:

| Section   | What it does                               |
| --------- | ------------------------------------------ |
| Servers   | The server enrol, inspect, console, update |
| Keys      | SSH public keys and their assignments      |
| Workflows | Compose and run scripted work              |
| Steps     | The reusable step library                  |
| Monitors  | HTTP, TCP, ICMP and TLS checks             |
| Secrets   | The encrypted vault                        |
| Audit     | Every mutating action                      |
| Settings  | Members, SSO, alerts, retention, licence   |

## 5. Add the rest of your team

Go to **Settings → Access**. Add members with a role:

| Role     | Can                                                |
| -------- | -------------------------------------------------- |
| `owner`  | Everything, including billing-adjacent settings    |
| `admin`  | Everything except owner-only settings              |
| `member` | Day-to-day work servers, keys, workflows, monitors |

Settings and organisation management require `owner` or `admin`.

If you would rather not manage passwords, configure single sign-on instead: see [Settings](../vantage/settings.md#single-sign-on).

You can add more than one identity provider; each gets its own button on the login page, and no buttons appear at all until at least one provider is configured.