Fall 2026 Overview
October 1 – December 31, 2026 · Matching phase
Season timeline
Items needing attention
Recent activity
Matching — Fall 2026
Review suggested matches, approve or replace, then save to Novi
Criteria: similar job title / role category · same region of North America · shared platform · admin note keywords · specific requests honored first · never same institution · never a repeat pair. Approve or replace each group individually. Approved matches write back to Novi.
No matches generated yet
Click Generate matches to create suggested groups. Prior connection history is automatically excluded.
Participants
All LinkUp registrants · click any row for full history
| Name | School | Role | State | Seasons | Status |
|---|
Communications — Fall 2026
Sender: linkup@naccu.org (Reply-To: john@naccu.org)
Check-in responses
Monthly survey — each pair gets a personal link, no login needed on their end
Reports & Analytics
Connection history across all LinkUp seasons
Participation by state / province
Season comparison
Summer 202666 participants · match count pending sync
Fall 202656 registered (still open) · matching in progress
Check-in response rates by month (example figures — pending real sync)
Summer 2026 — Month 1— %
Summer 2026 — Month 2— %
Fall 2026 — Month 10% (not started)
Connection history — all time
Rows below are example layout only — not real NACCU participants. Sync Summer 2026 from Novi to populate this with actual connection history.
| Participant | School | Season | Match 1 | Match 2 | Match 3 | Engagement |
|---|---|---|---|---|---|---|
| [Example Name] | [Example School] | Summer 2026 | [Partner] | [Partner] | — | Responded ✓ |
| [Example Name] | [Example School] | Summer 2026 | [Partner] | [Partner] | [Partner] | All 3 ✓ |
| [Example Name] ⚑ | [Example School] | Summer 2026 | [Partner] | — | — | No responses |
Settings
Novi AMS connection
Novi's API can't be called directly from a browser (confirmed with Novi support — no CORS support). Requests now route through a small proxy (Cloudflare Worker) that holds the real Novi API keys as encrypted secrets. This app never sees or stores those keys anymore.
The two test buttons check the proxy's NOVI_MEMBERS_API_KEY and NOVI_EVENT_API_KEY secrets independently, in case one is set up and the other isn't yet.
Institution directory (for wider-network matching)
Upload Novi's full member export (CSV) each quarter, around registration close. This caches every institution's real card system, access control, and printer — used when someone's LU Add Info requests a technology nobody in the current LinkUp pool has, so John can be shown real options from the wider NACCU membership instead of coming up empty.
Summer 2026 history backfill
One-time action: writes John's confirmed Summer 2026 pairings (91 real pairs, 56 people) into the "LU Partner 1/2/3 Summer 2026" fields. Requires Summer 2026 to be synced from Novi first (switch the season selector, then Sync from Novi) so names can be matched to real Novi records.
Microsoft Outlook (Graph API)
Same fix as Novi: Tenant ID / Client ID / Client Secret now live only in the Worker's encrypted secrets — never in this app or browser. This card just confirms the connection and sets who mail appears to come from.
linkup@naccu.org is no-reply. It's the sending address only. Anyone who replies to a LinkUp email, or reaches out about the program, should be told to use john@naccu.org — that's the monitored inbox. Worth making sure every email template signs off with that address.
Matching rules
These toggles gate the real matching engine directly — same-institution block, no-repeat-pair, role/region scoring, admin-note keywords, and honoring specific requests are all live behaviors in
scorePair()/splitByRequest(), switched by the toggles below. Changes apply the next time "Generate matches" is run — not to groups already on the Matching page.Block same-institution matches
Never match two people from the same school
Block prior-season matches
Never repeat a pair from any prior season
Prioritize role similarity
Match directors with directors, managers with managers
Prioritize regional proximity
Match within same North American region where possible
Consider admin note keywords
John's notes inform or override the algorithm
Honor specific match requests
Flag when a registrant named a specific person
Check-in & flags
Flags on the Check-ins page are now computed from real response data using these settings. There's deliberately no unattended background automation — "auto-reminder" here means the manual Send reminders now button on the Check-ins page is enabled, not a timer; it sends real email immediately when John clicks it.
Enable reminders for non-responders
Enables the manual "Send reminders now" button
Flag after 2 missed check-ins
Flag for John's review if two months' check-ins went unanswered by both people
Flag also if a partner reports low value
Based on the real "Was the connection valuable?" answer on a check-in