DocumentationFirst admin and organization
Docs/First admin and organization

First administrator and organization

The initial administrator is a bootstrap ceremony, not a permanent shared credential. Complete it from a private workstation and move the result into normal named-user administration.

Open the public base URL from the installer. The page is headed Welcome back.

Welcome back sign-in screen with password and SSO choices

  1. Enter the bootstrap email.
  2. Enter the one-time password printed by the installer.
  3. Select Sign in.

The control plane blocks organization routes until the forced password change is complete.

On Set a new password:

  1. Enter Current password using the bootstrap value.
  2. Enter New password.
  3. Repeat it in Confirm new password.
  4. Select Set password.

If the confirmation does not match or the API rejects the password, the form stays open. Do not reuse the bootstrap password elsewhere.

A user without a verified email may see Verify your email instead of the organization form. Follow the link delivered by SMTP, or use the manual link handoff your deployment administrator received when mail delivery is disabled.

Verification, reset, and invitation URLs are bearer secrets. Share them through an authenticated private channel and never publish them in docs or screenshots.

On Create your organization:

  1. Enter Organization name, for example Acme Corp.
  2. Review the generated Slug. It is normalized to lowercase and becomes the confirmation value for destructive organization operations.
  3. Select Create organization.

Errors such as invitation_required or org_limit_reached are authoritative; do not try to work around them by creating another bootstrap user.

After creation, Settings → Organization shows the active organization and the organization switcher.

Organization settings and tenant switcher

The fixture contains two synthetic organizations to demonstrate switching.

The creator becomes an owner. Before production:

  1. Invite a second named administrator or owner.
  2. Confirm both people can sign in independently.
  3. Configure MFA for both accounts.
  4. Record who controls the host, DNS, backup key custody, and IdP fallback.

Do not deactivate owners sequentially without confirming a usable owner remains. The current owner-count guard can include a deactivated owner; keep an active, tested recovery owner until that edge case is removed.

From the sign-in page, select Forgot password?, enter the account email, and select Send reset link.

Forgot-password form

When SMTP is disabled, email delivery cannot complete even though local password sign-in still works. An organization administrator can also use Users & Roles → Reset 2FA for another user; password reset and MFA reset are separate operations.

You should reach Overview with your organization name and fleet summary.

Control-plane overview after onboarding

Before enrolling anything, make the initial database-plus-master-key backup described in Backup and restore. Then continue with Gateways.

Documentation

Search Tunnex docs