After installation

First sign-in and setup

Create the first Admin, choose the modules you want, and get Attendance ready for your first meeting.

Open the dashboard link from the installation run summary. It has the form https://<slug>-dashboard.pages.dev. Keep your password manager open: you need the LANCERLOGIN_SETUP_CODE value you saved during installation.

1. Create your installation

A new installation opens the Create your installation form. Fill in each field:

FieldWhat to enter
One-time setup codeThe LANCERLOGIN_SETUP_CODE secret value, at least 16 characters.
Organization nameThe name members see on the dashboard and kiosks. You can change it later.
Time zoneChoose your organization's time zone from the list. Meeting times, reports, and attendance windows use it.
Dashboard sign-inUsername and password, Google OAuth, or Both methods. Google needs a client ID and secret first; see Google sign-in.
Admin username, Admin password, and Confirm Admin passwordFor password sign-in. The password must be at least 12 characters.
LancerLogin Create your installation form with fields for One-time setup code, Organization name, Time zone set to America/New York, a Dashboard sign-in choice of Username and password, Google OAuth or Both methods, Admin username, Admin password with the hint At least 12 characters, Confirm Admin password, and the Create first Admin button.
The first-time setup form.

Select Create first Admin. LancerLogin creates the installation and, for password sign-in, signs you in as its first Admin straight away. After this, the setup code cannot create another Admin.

Setup code not accepted? Check for extra spaces from copying. To use a new code, update the LANCERLOGIN_SETUP_CODE secret and run the installation workflow again with operation resume and the same slug. This works only while no Admin exists.

2. Choose modules

Next, Choose modules lists the modules this installation includes. Core always provides accounts, roster, labels, reports, branding, integrations, backups, and updates; modules add workflows on top of Core. Each module is marked Built-in or Plugin, and Attendance is selected and marked Recommended.

LancerLogin Choose modules screen listing Attendance with Built-in and Recommended badges and its switch on, Outreach Participation and Carpool with Plugin badges and their switches off, and a Continue button.
Attendance is selected by default. Plugins can be turned on now or later.

Select Continue.

3. Attendance setup

Attendance setup shows one card at a time, with progress such as "Step 1 of 6" and "0 of 4 required steps complete". Each card saves when you choose Save and continue. Finish setup later keeps the steps you saved; Attendance becomes available once every required step is complete.

  1. Attendance rules sets Late scan minutes (how long after a meeting ends check-ins are still accepted), Reporting starts on (optional; reports count meetings from this date), and the Late anomaly threshold (minutes) and Early anomaly threshold (minutes) that flag late arrivals and early departures. Member labels and attendance requirements can be added later.
  2. First meeting creates a test meeting that is happening now, so you can record a check-in in the next step.
  3. Roster adds at least one person. Enter Member ID, First name, Last name, and optionally Email, then choose Add member, or choose Import CSV. Choose Add another member for more. You can add everyone else later on Roster.
  4. Verified attendance input pairs your first kiosk: a Raspberry Pi with a fingerprint reader, or a touchscreen laptop or tablet as a web kiosk. Choose Add kiosk on the card; it is the same dialog as Kiosks › Add kiosk, and Kiosks explains both kinds. The step is complete once the kiosk checks in, usually within a minute of pairing, and the card updates on its own. The kiosk takes attendance once setup is finished.
  5. Calendar integration is marked Optional. Choose Open Integrations settings to connect Google Calendar, or Set up later and continue.
  6. Discord integration is also Optional, with the same two choices. See Discord member commands.
LancerLogin Attendance setup at Step 1 of 6 with 0 of 4 required steps complete. The required Attendance rules card has Late scan minutes set to 30, an empty Reporting starts on date, Late and Early anomaly thresholds of 10 minutes with help text for each, and Back and Save and continue buttons, with Finish setup later below.
Step 1, Attendance rules, with help text under each field.
LancerLogin Attendance setup at Step 3 of 6 with 2 of 4 required steps complete. The required Roster card asks to add at least one person and has Member ID, First name, Last name and optional Email fields with Import CSV and Add member buttons.
Step 3, Roster: add at least one person.
LancerLogin Attendance setup at Step 4 of 6 with 3 of 4 required steps complete. The Verified attendance input card, marked Ready, asks to pair a Raspberry Pi or a web kiosk, lists Test web kiosk as checked in, confirms that a paired kiosk has checked in, and has Add kiosk, Back and Save and continue buttons.
Step 4, Verified attendance input, completes once a paired kiosk checks in.

4. Attendance is ready

After the last card, the completion screen says Attendance is ready and offers optional next steps: Add more kiosks, Add or import members, Invite other Admins, Connect Google Calendar or Discord, and Set up dashboard updates. Choose Go to Meetings to start. The primary navigation now shows Meetings, Roster, Reports, Kiosks, and Settings, plus a page for each plugin you turned on.

LancerLogin Attendance is ready screen with optional next steps Add more kiosks, Add or import members, Invite other Admins, Connect Google Calendar or Discord, and Set up dashboard updates, and a Go to Meetings button.
The completion screen lists optional next steps.

To review the setup cards later, open Settings › Modules › Attendance › Attendance setup and choose Open Attendance setup. Reopening setup does not change existing meetings or attendance.

Next steps