In this update, I built the backend Ruby server and set up the initial database schema. First, I created the authentication table to handle login functionality, then implemented route protection around the /dashboard endpoint. Unauthenticated users attempting to access protected routes are redirected back to the login page, while authenticated users are directed to the specific view assigned to their role.Second, I built out database tables for the four main user types: Students, Guidance Counselors, Teachers, and Admissions Staff. Establishing these base models and access controls sets up the foundation needed to build out role-specific permissions and workflows in upcoming updates.