Lux AF — Admin

🏢

Buildings in Portfolio

👤

Total Applicants

⏳

Pending Review

✓

Placed This Month

🏆

Placed Overall

💰

Commission This Month

💵

Commission Overall

Recent Applicants

Latest submissions

Name	Budget	Status	Submitted

Activity

Recent updates

Applicants by Source

Where clients found us

Building	Portfolio	City	ZIP	Units	Avail	Unit Mix	Rent Range	Fee to Agent	Last Call

Name	Moving From	Desired Area	Budget	Status	Agent	Date

Name	Email	Phone	Status

Community	City	Phone	Notes	Added

Username	Role	Status	Created

Sent	Type	Recipient	Subject	Applicant	Status

💰

Total Earned

✓

Collected

⏳

Outstanding

📄

Invoiced

Invoice #	Date	Client	Building	Agent	Commission	Status

MySQL API Connection

Live — connected to MySQL

API Base URL

Your domain + /api — e.g. https://luxaf.com/api

API Secret Key

Must match the API_KEY value in api/config.php.

Email Notifications

When an applicant submits the frontend form, your PHP API automatically sends two emails: a confirmation to the applicant and an alert to you. Enter your email address below to receive those alerts.

Admin Notification Email

This is saved here for reference — the actual address is set in api/config.php under ADMIN_EMAIL. Both are checked; the config.php value is the fallback.

Applicant Confirmation Email

This is the automatic email sent to every applicant right after they submit the frontend form. Edit the copy below — changes take effect on the next submission, no code changes needed. Available tokens: {{firstName}} {{lastName}} {{desiredArea}} {{budgetMin}} {{budgetMax}} {{bedrooms}} {{moveInDate}} {{lifestyle}}

Subject Line Intro Paragraph (shown above the Search Summary box) Benefit & Touring Note (shown below the Search Summary box — HTML allowed)

Placement Thank-You & Review Request

Sent automatically the moment an applicant's status is changed to Placed (won't resend if the record is saved again while already Placed). By design this asks for one review — on the Lux AF Google Business Profile — and names the assigned agent in the copy so they get credit without a second, separate ask.

⚠️ The button below links to a placeholder Google review URL. Replace https://g.page/r/REPLACE-WITH-YOUR-GOOGLE-REVIEW-LINK/review in the body field with your actual Lux AF Google review link before this goes live, or clients will land on a dead link.

Available tokens: {{firstName}} {{lastName}} {{buildingMention}} {{agentMention}} {{buildingName}} {{agentName}}

The …Mention tokens are full, pre-written phrases (e.g. " at The Meridian" or " Feel free to mention Jordan Miles…") that collapse to nothing when there's no building/agent on file — use those in sentences so the copy still reads naturally either way. Use the bare {{buildingName}}/{{agentName}} only if you're building your own sentence around them.

Subject Line Intro Paragraph (shown right under the "Hi {{firstName}}," greeting) Review Ask (shown below the intro — HTML allowed; this is where the Google review button lives)

Sends the saved version above (hit Save Template first if you just edited it), with sample data — "Alex Rivera" — and a real agent/building pulled in if one's on file. Marked [TEST] and logged separately in the Email Log.

Touring Policy Email

Sent automatically the moment an applicant's status is changed to Approved (won't resend if the record is saved again while already Approved). Explains that tours go through Lux AF and that we can only arrange tours at vetted partner buildings — sets expectations before a client's first tour. See lux-client-touring-sop.md for the underlying policy this is based on.

Available tokens: {{firstName}} {{lastName}}

Subject Line Intro Paragraph (shown right under the "Hi {{firstName}}," greeting) Policy Explanation (shown below the intro — HTML allowed)

Sends the saved version above (hit Save Template first if you just edited it), with sample data — "Alex Rivera". Marked [TEST] and logged separately in the Email Log.

NJ Cities (Frontend Display)

These cities appear on the frontend form and the city chips section. Add or remove as your market coverage changes.

"How did you hear about us?" Options

These appear as dropdown choices on the frontend form and the admin applicant modal. Add or remove as your marketing channels change. "Other" is always included automatically and can't be removed — it has its own free-text follow-up field.

Admin Login Credentials

Login credentials are stored in the HTML source. To change them, open lux-admin.html in a text editor, search for const CREDS, and update the usernames and passwords. Re-upload the file when done.

⚠️ Do not share this admin URL publicly — it has no server-side access control beyond the login screen.

Changing Admin Password

Passwords are stored in the HTML source. To change them, open lux-admin.html in a text editor and find the CREDS object near the bottom.

Open lux-admin.html in a code editor

Search for const CREDS and update the usernames/passwords

Re-upload the file to Hostinger

Database Setup Instructions (Hostinger MySQL)

Follow these steps to go from Demo Mode to a live database on your existing Hostinger plan.

Log into Hostinger hPanel → Databases → MySQL Databases → Create a new database and user

Open phpMyAdmin, select your new database, click the SQL tab, paste the contents of lux-mysql-setup.sql, and click Go

Open api/config.php and fill in DB_HOST, DB_NAME, DB_USER, DB_PASS, and set your own API_KEY

Upload the entire api/ folder to your Hostinger public_html/ directory (alongside the HTML files)

In this Settings tab, enter your API Base URL (e.g. https://yourdomain.com/api) and your API Key → Save & Connect