Release Notes

Signing in with Google is faster — no more unnecessary database lookups for new users.

When someone signs up to NavEd using Google for the first time without an invitation link, our system was quietly running 36 extra database queries in the background trying to find invitation data that didn't exist. The signup itself succeeded, but those extra round-trips added over a second of unnecessary processing time on every organic Google OAuth signup.

We've added a guard that detects uninvited signups immediately and skips the database scan entirely. Invited users are unaffected — their invitation data is still found and applied correctly.

Fixes and Improvements¶

• Organic Google sign-ups no longer trigger an unnecessary cross-school database scan
• Added self-healing: stale invitation routing records are now corrected automatically on first login

A student account in an unusual state was seeing a server error on subject and grade pages—that's fixed.

In rare cases, a student account can end up without a complete profile record behind it (for example, if the account was created during a brief setup window that didn't complete successfully). When that happened, any page that needed to look up the student's grades, clubs, or subject documents would crash with a 500 error instead of handling the situation gracefully.

We've added defensive error handling across subject overview, grade pages, subject documents, and the clubs list so that if a student account is ever in this incomplete state, the page either loads safely with no data or shows a clear message asking the student to contact their school administrator—no more crashes. We also fixed a typo in a page template that would have prevented the subject documents form from submitting correctly for any user.

Fixes and Improvements¶

• Fixed 500 error on subject overview pages for accounts with incomplete student profiles
• Fixed 500 error on grade pages for accounts with incomplete student profiles
• Fixed 500 error on subject documents pages for accounts with incomplete student profiles
• Fixed 500 error on clubs list page for accounts with incomplete student profiles
• Fixed a broken form action URL in the subject documents template

A new blog post was hiding from search engines—we found it and brought it back.

Our "What Is Standards-Based Grading?" article published this week, but because of a small formatting quirk in the file, it never made it into our sitemap. Search engines like Google and Bing use the sitemap to discover new content, so without that entry, the post was effectively invisible to anyone searching for it.

The post itself was always accessible if you had the direct link, but we want every piece of content we write for educators to be as easy to find as possible. We've fixed the post and added a safeguard so that similar formatting issues in future posts won't cause the same silent disappearance.

Fixes and Improvements¶

• Restored standards-based-grading-guide to the sitemap so search engines can index it
• Added a defensive check in the blog post parser to handle formatting edge cases gracefully

The Payment Settings page just got a fresh coat of paint—and a few thoughtful touches.

We redesigned the Payment Settings and Stripe onboarding pages to match the rest of NavEd's modern look. But it's not just cosmetic. We also made the experience friendlier for school administrators setting up payments for the first time.

The "Connect with Stripe" screen now features a trust message so you know your banking details are never stored by NavEd. We replaced technical Stripe jargon like "Accept Charges" and "Receive Payouts" with plain language—"Collect tuition payments" and "Receive funds to your bank." And if Stripe is reviewing your information, the page now clearly tells you no action is needed on your end.

Fixes and Improvements¶

• Added accessibility attributes to all decorative icons
• Upgraded the "Account Disconnected" alert to make the severity clearer

The gradebook now tells you what to do when quarters haven't been set up yet—instead of crashing.

If a teacher tried to open the gradebook for a subject whose school year hadn't been fully configured yet (specifically, no grading quarters set up), the page would return a server error. There was no explanation—just a blank failure. That's fixed.

Now, if you land on the gradebook tab and no quarters exist for that subject's session year, you'll see a clear message: "No grading quarters have been configured for this subject's session year. Please set up quarters before using the gradebook." The page stays up and points you toward the right next step.

Fixes and Improvements¶

• Fixed a 500 error when accessing the gradebook for a subject with no quarters configured
• The same guard was applied to the legacy grades view, closing an identical crash path

The Payments page now guides you through Stripe setup.

If you visit the Payments dashboard before connecting your school to Stripe, you'll now see a clear banner explaining your next step. Previously the page just showed empty data with no hint about what to do.

• If Stripe isn't configured in your environment, a warning explains that payment collection isn't available
• If your school hasn't started Stripe onboarding, a "Set Up Stripe" button takes you directly to Payment Settings
• If onboarding is in progress, a "Continue Setup" button appears so you can pick up where you left off
• Once Stripe is fully connected, no banner appears and the dashboard works as usual

Creating assignments in the gradebook now always ends in success—not a server error.

If a teacher accidentally checked both the "Midterm" and "Final" boxes when adding a regular assignment, the page would crash with a server error instead of showing a helpful message. That's now fixed.

The assignment form now catches this combination before it ever reaches the server, so you'll see a clear validation message right away. We also repaired a longstanding issue where the mutual-exclusion guard in the browser was silently broken—it just wasn't wired up correctly. Both the form and the browser now agree: an assignment can be one or the other, but not both.

Fixes and Improvements¶

• Fixed a 500 error when submitting the regular assignment form with both "Midterm" and "Final" checked simultaneously
• Activated the client-side mutual-exclusion guard for the Midterm and Final checkboxes (it was previously non-functional)
• Added server-side safety nets on all three assignment-creation paths in the gradebook so unexpected validation errors show a friendly message instead of crashing

Stripe Connect onboarding should no longer show a generic error.

If you clicked "Connect with Stripe" on the Payment Settings page and saw "Unable to start Stripe Connect onboarding. Please try again." with no further detail -- we've fixed that. The root cause was insufficient error handling that hid the actual problem (which could be anything from a misconfigured API key to a lost tenant context).

Now, if Stripe isn't properly configured, you'll see a specific message telling you to contact support. If the API call fails, the full error details are logged internally so we can diagnose the issue without asking you to reproduce it.

Fixes and Improvements¶

• Added pre-flight validation that catches misconfigured Stripe API keys before making API calls
• Improved error logging for faster debugging
• Fixed a scenario where tenant context loss could silently swallow the real error