I'll build a School Management SaaS application with dynamic RBAC-based module rendering using Next.js. This is a multi-system project, so let me set up a task list to track progress.

I have the design inspiration and project structure. Let me read the sidebar component since it exists, and then start building the authentication system and RBAC configuration.

I have everything I need. Let me now build the School Management SaaS application with RBAC. I'll start by creating the core authentication system and RBAC configuration.

Now let me move to the next task and build the dynamic sidebar and layout.

Now let me create the role-specific dashboards and update the globals.css with a professional dark theme.

Now let me create sample protected module pages and the login page.

Now let me create the remaining module pages for teacher, student, and parent roles:

Now let me create the login page and update the root layout and main page:

Now let me mark all tasks as done and verify the application is working:

I've successfully built the School Management SaaS application with a complete RBAC system. Here's what was implemented:

Core Architecture:

• RBAC Configuration (lib/rbac-config.ts): Defines all 5 roles (Super Admin, School Admin, Teacher, Student, Parent) with their respective modules, permissions, and paths
• Authentication Context (contexts/auth-context.tsx): Provides login/logout, role checking, and permission validation with demo accounts for testing
• Type Definitions (lib/auth-types.ts): TypeScript types for User, AuthResponse, and AuthState

Dynamic UI Components:

• App Sidebar (components/app-sidebar.tsx): Dynamically renders navigation based on the logged-in user's role - no hardcoded menu items
• Dashboard Layout (app/dashboard/layout.tsx): Protects routes and redirects unauthorized users
• Module Page Template (components/module-page.tsx): Reusable component that checks permissions and displays module content

Role-Specific Dashboards:

• Each role sees different stats and modules on their dashboard
• Read-only modules are clearly marked with badges
• Unauthorized route access is blocked with proper redirects

Demo Accounts for Testing: