Sign-In Errors Now Tell You What's Actually Wrong—and Support Can Switch District Context
Getting a generic "access denied" message when you're locked out is infuriating. Not knowing whether you need to sign in again or whether your account simply doesn't have permission for that event leads to unnecessary support calls—and unnecessary frustration.
Specific error messages replace generic access denied
Sign-in and access errors now communicate the real reason clearly. "Your session has expired—please sign in again" is a different message from "You don't have permission to access this event," and users now see the appropriate one. This distinction alone eliminates a significant share of "I can't log in" tickets that were actually session expiry issues.
For support team members who assist multiple districts, this release adds the ability to switch district context within the admin interface without signing out and back in. Troubleshooting a configuration issue for a specific district is now a context switch, not a full re-authentication cycle. Paired with SSO support for district-managed accounts, this makes the support workflow significantly more efficient.