We've added an AI Help Desk feature to the school dashboard, allowing schools to manage support requests, conversation history, and identify gaps in AI knowledge. The feature is opt-in by default to ensure schools maintain control over their AI usage budget. It includes full support for ticket management, screenshot handling, and a 30-day data retention policy.

We've added the ability for administrators to set a default sidebar navigation style (Classic or New) at the tenant level. This setting is now exposed through the tenant configuration API and is respected by the school app while still allowing individual users to override their preference in their appearance settings. This change includes an additive database schema update and full support for backup snapshots.

This update adds flexible UI terminology renaming, allowing tenants to customize specific terms like 'classTracker' or 'routine' via a new administrative interface, with validation to prevent markup or control character injection. We've also introduced a 'DEPARTMENT_VIEW' feature flag, which is disabled by default, to gate a new read-only department dashboard that aggregates teacher progress and attendance metrics. These changes provide more tenant-specific customization and safer feature rollouts.

Updated the cron status UI to explicitly label new, not-yet-run jobs as 'Waiting for first run' instead of just generic pending states. This provides better visibility into the lifecycle of newly deployed background tasks.

Added a new monitoring system for scheduled background jobs across tenants by polling individual /api/control/cron/status endpoints. The status data is now persisted in TenantCronStatus, enabling a new "Scheduled jobs" dashboard card and visual flagging of late or failing jobs directly within the tenant list view. This provides visibility into the health of critical background tasks across all managed school instances.

Introduced a new TEACHER_ATTENDANCE feature flag to the platform, enabling geofenced check-ins for teachers independently of student attendance. The change includes updated Prisma schema definitions and TypeScript types to support this new setting. A backfill script was also included to ensure all pre-existing tenants have this feature enabled by default.

Introduced a new PAYMENTS feature flag to the Prisma schema and updated the shared types. This allows for granular control over tuition-payment eligibility and associated enforcement settings at the tenant level.

Introduced a new one-shot migration script to ensure existing tenants correctly receive default enabled states for features like API, Webhooks, and Backlog. Previously, older tenants lacked these rows in the database, causing them to appear disabled even when the intended default was on. This script safely backfills missing records without overriding any manual changes an admin may have already made.

We've introduced a new fleet-wide analytics dashboard that provides visibility into tenant engagement. It uses a new nightly cron job (/api/cron/analytics-sync) to pull and cache engagement snapshots, ensuring the admin dashboard remains fast and resilient even if individual tenant instances are offline. Users can now view aggregated metrics across the fleet or drill down into specific tenants, with built-in fallbacks to cached data if live connection fails.

We updated the tenant backup API to run a cleanup of stale, dead jobs whenever the backup list is requested. Previously, if a backup agent crashed before its first heartbeat, it would sit in a 'PENDING' state indefinitely, blocking new backups and silently disabling the system until the nightly cron job ran. This change ensures that dead jobs are cleared immediately upon access, preventing service disruption.

Updated layout components across dashboard views to refine element sizing and alignment, ensuring a more polished and consistent user interface. This refactor specifically targets the tenant backup and main dashboard pages, streamlining component structures to better handle varied content. The changes improve overall layout responsiveness and visual stability.

Simplified the dashboard layout by replacing nested flex containers and manual overflow management with a more robust sticky-sidebar, native-scroll approach. This eliminates common CSS pitfalls like double scrollbars and sizing issues caused by flex height chains, ensuring a smoother user experience as content grows.

Added support for 'OSM' (On-Screen Marking) and 'TRANSCRIPT' features to the platform schema. Corresponding labels and descriptions were updated in the frontend utility types to ensure they are properly exposed throughout the application. These additions allow for granular tenant-level configuration of these new assessment and reporting tools.

We have established the foundational database schema using Prisma, introducing core models for Admin, Tenants, and secure API Key management. This includes robust support for multi-tenancy with isolated features and API access controls. These changes set the stage for our upcoming infrastructure work and exports consistent TypeScript types for end-to-end type safety across the stack.

We have successfully scaffolded the foundation for our new admin panel, including essential authentication flows and a suite of reusable UI components. This initial commit sets up the dashboard layout, tenant management structure, and shared elements like buttons and badges to ensure consistency. It provides a solid baseline for rapidly building out the remaining administrative features.

We've added a new tenant management module which includes comprehensive support for creating and editing tenant records. This update encompasses necessary Prisma schema migrations along with new UI components and API routes to handle tenant data efficiently.

We have successfully rolled out multi-tenant infrastructure support, including necessary database schema updates in Prisma and new API endpoints for tenant configuration. This update also adds a dedicated admin UI for managing tenant settings, streamlining the onboarding and management process for multiple tenants. This unlocks architectural support for scaling our platform across isolated client environments.

We've established the core data architecture by initializing the Prisma schema with essential models for Tenants, feature flags, and API key management. This provides the foundational structure for multi-tenant isolation and per-tenant configuration across our application services.

Added a secure admin login route featuring credential-based authentication and integrated loading states to improve user experience during requests. This update establishes the foundation for restricted administrative access within the application.

Added a postinstall script to package.json to ensure the Prisma client is automatically generated after dependency installation. This eliminates the need for manual generation steps when setting up the project, ensuring the generated client is always available and in sync with the schema after npm install or yarn install.