Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Taykl12/Classify/llms.txt

Use this file to discover all available pages before exploring further.

Every account created through the Classify registration flow starts as a student (alumno). Students are the primary users of the platform — they own and contribute to projects, break work down into tasks, and stay on top of deadlines through the calendar. While students cannot access professor or admin features, they have full control over their own project workspace from the moment they sign up.

​
Registration and Role Assignment

When a user submits the registration form, the platform calls POST /api/auth/register. This endpoint creates a new Supabase Auth user and inserts a corresponding row in the usuarios table with id_rol = 3 (alumno). No admin action is required — the role is applied automatically and takes effect on the very first login. 
POST /api/auth/register
→ Creates Supabase Auth user
→ Inserts usuarios row with id_rol = 3

​
What Students Can Do

Students can create new projects, view the full details of any project they belong to, and edit project metadata. The user who creates a project becomes its owner; all other members who join later are collaborators.Owner privileges (vs. collaborators)
ActionOwnerCollaborator
Edit project name / description✅❌
Delete the project✅❌
Invite new members✅❌
View project details✅✅
Create and edit tasks✅✅
Mark tasks complete✅✅
Inside each project, students can create tasks, assign them to members, set due dates, and mark them as complete. The dashboard surfaces pending tasks so students always know what needs attention next.
The calendar view at /calendario aggregates events tied to the student’s projects. Students can view upcoming deadlines and scheduled events in one place but cannot modify events added by professors or administrators.
Students can update their own profile and preferences from /configuracion-proyecto/:id. They cannot modify other users’ accounts or change their own role.

​
Frontend Routes

RouteDescription
/dashboardPersonal dashboard with featured project and pending tasks
/proyectosList of all projects the student belongs to
/proyectos/:idDetail view for a specific project
/calendarioCalendar of project events and deadlines
/configuracion-proyecto/:idProject settings (owner-only actions gated in UI)
All of these routes are wrapped in <ProtectedRoute>, which requires a valid session. Unauthenticated visitors are redirected to the login page.

​
What Students Cannot Do

Students do not have access to professor or admin functionality. Attempting to reach protected routes redirects them to their own dashboard.
  • Access /profesor/* routes or any professor API endpoints
  • Access /admin/* routes or any admin API endpoints
  • Record or view attendance records
  • Validate pre-projects (anteproyecto_validado)
  • Lock project sections (scope, documentation, team)
  • Promote or demote other users

​
Project Ownership vs. Membership

When a student creates a project, they are stored as its owner. Ownership determines who can change project-level settings such as the name, description, and member list. Collaborators who are added later share the project workspace — they can create tasks and contribute content — but cannot alter the project configuration or remove members. If you need a project collaborator to take over ownership, an admin can update the project record directly from the admin panel.

Build docs developers (and LLMs) love

Get started for freeTalk to us