Skip to content

Designate the first administrator with FANOUT_FIRST_ADMIN_EMAIL #427

Closed

Description

@vishr

What

Add FANOUT_FIRST_ADMIN_EMAIL. When the control database has no users and the setting is present, Fanout creates the first administrator as an active administrator instead of printing the one-time setup URL, and never changes existing accounts. Because no setup call happens, the first administrator must also be able to issue the first ingest token from the UI or POST /api/settings/ingest/token/rotate when none exists yet.

Acceptance criteria

  • With the setting, no setup URL is printed and the owner can sign in with an email code or fanout login-link
  • Without the setting, first boot behaves as today
  • The owner can issue the first ingest token when none exists
  • Configuration reference regenerated

References

  • site/src/content/docs/docs/get-started/first-boot.mdx
  • internal/config

One pull request. Use the latest stable version of any dependency added, verified against its registry and pinned exactly.

Activity

  1. added theissue type on Nov 7, 2026
  2. changed the title [-]Designate the first administrator with FANOUT_OWNER_EMAIL[/-] [+]Designate the first administrator with FANOUT_FIRST_ADMIN_EMAIL[/+] on Nov 7, 2026
  3. vishr commented on Nov 8, 2026

    @vishr
    MemberAuthor

    Reverted before any release in #448. Automated installs will create accounts through SCIM provisioning (#442) instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions