Finlay.worksBareBones Ticketing manual

Install

First Administrator

How to create the first System Administrator account at /setup, and when that route is open.

RC2 approved for evaluation Status: release-candidate Audience: System Administrator Source: c4b4d41

First Administrator

The /setup page creates the first System Administrator account. At this point no accounts exist at all.

Setup runs only while no active SystemAdmin grant is in force. The product re-evaluates this every time the page loads, against the accounts, grants, and groups that are active at that moment. Deactivating the last System Administrator, its grant, or the group that carries the grant reopens /setup.

The check has a second branch. If an active group holds the SystemAdmin grant, setup is closed regardless of who is in that group. An active group with no members closes /setup even though no administrator account exists.

Before you start

  • The application installed and running. If it is not, go to Windows Server or Linux Docker Compose first.
  • The HTTPS address of your installation.
  • Your organization's legal name, as it should appear on the licence.
  • A username, display name, and password for the first administrator. The password minimum is 8 characters. Apply your own policy if it is stricter.
  • The Product License Agreement, which ships with the package.
  • Authority to accept that agreement for the organization you are naming.

The installer already set up the database. This page does not. If the installer reported a database problem, fix that first — the application will not start otherwise. See PostgreSQL.

Create the account

  1. Open /setup at your installation's HTTPS address.

  2. Read what the page says.

    • Create the first system administrator — continue to step 3.
    • System setup has already been completed — stop. An administrator already exists. Sign in normally.

  3. Enter your Licensee Company or Organization.

  4. Enter the first administrator's Username and Display Name.

  5. Enter the password, then confirm it.

  6. Open the Product License Agreement and read it.

    If the page reports the agreement as missing, stop. Do not create the administrator. Return the package to whoever supplied it.

    The product does not enforce this. The alert appears, but the acknowledgement checkbox and the submit button stay enabled, and setup will create the administrator without the agreement present. Stopping is your decision.

  7. Select Acknowledge and Create System Admin, once.

    The account is created and the acknowledgement is recorded. /setup now reports that setup is complete.

  8. Sign in with the account you just created.

Check it worked

  • /setup reports that setup is complete.
  • You can sign in as the new administrator.

If it does not work

Setup says an administrator already exists. Sign in normally. Do not look for a way around bootstrap; there is not one.

The Product License Agreement is missing. Stop before creating the administrator. Return the package to the release owner. The product will let you continue; do not.

The form fails to submit. Read the error. Check the database prerequisites and your input. Do not retry repeatedly. Escalate without sharing the password or private deployment details.

The application will not start, and the error mentions schema or runtime authority. Go back to the package's database assistant. See PostgreSQL. Do not grant the runtime database identity migration, DDL, ownership, or audit-write authority.

Setup succeeded but sign-in fails. Stop. Do not create another administrator and do not retry the password repeatedly. Check the address and username, keep the error, and escalate.

Next step

HTTPS and hostnames, then Licensing.

If you already set your approved hosts and certificate, go straight to Licensing.