Site Administration

Logins and Passwords

Every m77ag.com login: admins, employees, landlords, farmers and bankers. Create a login, set a new password, email a set-password link, turn a login off, and choose which farms a landlord sees.

• Passwords are stored encrypted (bcrypt). No one, admin included, can read a password back. To get someone in, set a new password or email them a reset link.
• Anyone can reset their own password from Forgot your password? on the sign-in pages. The emailed link works for one hour.
• Landlords can change their password on their dashboard, under Preferences.
• One email holds one login. A person who is both an admin and a landlord needs two emails (for example admin@togoag.com for admin, kyle@togoag.com for the KBFARMS landlord login).

Partner Accounts

Partner portal accounts: create, approve and manage them, and review pending registrations.

Handbook: How m77ag.com Is Built

Sections: What the site does · Where everything lives · Technology · How the code is organized · How a change goes live · Settings and secrets · Scheduled jobs · Farm records rules · When something breaks · Taking over the site

What the site does

m77ag.com is the business system for M77 AG LLC and the related McConnell businesses, built by Kyle McConnell. It has a public website and private portals:

• Public: home page, custom farming services and rate calculator, hunting leases (Heritage Farm, Prairie Peace) with bookings, waivers and season passes, equipment for sale, rentals.
• Admin (/admin): field records and field cards, farm books, season calendar, soils, equipment, cattle and calf crop, Financial (bills, check printing, expenses, banking, tax), Mail Center, landlords, employees, hunting bookings.
• Landlord portal (/landlord): each landlord sees their own farms read only, with their pay-now balance.
• Farmer, tenant, land management and customer portals.

Where everything lives

Technology

How the code is organized

public/            pages people see (admin/, landlord/, js/, css/, assets/)
server/server.js   starts the site, connects the database, mounts every /api route
server/routes/     the API: one file per area (cattle, field-ledger, accounts, ...)
server/controllers/ the logic behind larger routes
server/models/     database record shapes (User, CroppingField, FieldOperation, ...)
server/services/   shared calculations (bills owed, calf crop, bank reconciliation, ...)
server/data/       farm records entered from Kyle's documents (statements, tickets,
                   settlements, cattle feed), one file per subject, each citing its source
server/middleware/ sign-in and access checks (auth.js)
docs/              rules and audits (farm-records-2026.md, audits/)
CLAUDE.md          the working guide for the code: design rules, conventions, routes

Design rules (in CLAUDE.md): professional tone, no emojis, mobile first, colors #2d5016 / #2c5530 green and #d4a54a gold on #f5f3f0.

How a change goes live

1. Make the change on a branch of mcconnellentllc-cloud/m77ag (GitHub Desktop, the GitHub site, or a Claude Code session).
2. Open a pull request into main and squash merge it.
3. Render sees the change on main, runs npm install, then npm start. The new version is live in a few minutes. Build and run logs are in the Render dashboard.

To run the site on a computer for testing:

git clone https://github.com/mcconnellentllc-cloud/m77ag
cd m77ag
npm install
(create a file named .env with the settings below; never commit it)
npm run dev        then open http://localhost:3000

Health check: https://m77ag.com/api/test answers with the API and database status.

Settings and secrets

Every key and password the server uses is a setting (environment variable) in the Render dashboard, m77ag service, Environment. The code reads them by name; their values are never stored in the code or on this page.

Scheduled jobs

• Rental billing (Mountain time): monthly invoices on the 1st at 6 AM, payment reminders daily at 9 AM, late fees on the 6th at 8 AM (when ENABLE_BILLING_CRON is on).
• Life assistant: runs hourly from 6 AM to 8 PM Mountain time.
• Mail Center sync every MAIL_SYNC_MINUTES; John Deere sync every JD_OPS_SYNC_HOURS.

Farm records rules

• How costs are spread and billed on the field cards, the Lueking operating line and custom work: docs/farm-records-2026.md. Read it before changing any field record, allocation or billing.
• JD Operations Center is the authority for field names and acres; the locked rotation plan is the authority for crops.
• Records entered from documents (statements, tickets, settlements) live in server/data/ with the source named in each file. Nothing is estimated without saying so.
• QuickBooks is the book of record through Dec 31, 2026.

When something breaks

• Site down or erroring: Render dashboard, m77ag service, Logs. A failed deploy can be rolled back there to the last good one.
• Database errors: check MONGODB_URI and that MongoDB Atlas network access allows Render.
• Email not sending: run npm run check:email; SMTP AUTH must be on for the sending account in the Microsoft 365 admin center.
• John Deere disconnected: reconnect with Connect to John Deere on the admin Fields page (/admin/fields.html); the OAuth app is on developer.deere.com.
• Someone locked out: Accounts page, Set Password or Email Reset Link.

Taking over the site

To keep m77ag.com running, the next person needs owner access to each of these accounts. Record who holds each one and where its sign-in is kept:

A developer new to the site should start with CLAUDE.md in the repository, then docs/farm-records-2026.md. The site was built and is maintained with Claude Code; a new Claude Code session on the repository reads CLAUDE.md automatically and can carry on the work.