How luan-h/multiagenda works
MultiAgenda is a Django-based, multi-company appointment-management system backed by PostgreSQL and raw SQL. Staff or clients enter through routed views; the system manages accounts, professionals, clients and services, then displays and saves appointments against professional availability. The documented agenda engine generates 30-minute slots for 30 days from each professional’s weekly schedule. The graph separates request handling from domain models and storage. Evidence is strongest for the sampled views, model relationships and URL routing; unsampled implementation details are not inferred.
Main entry points: urls.py URL routing · empresa/models.py Company records · agenda/models.py Agenda slots · views.py Professional management
Components 16
Web workflows
- URL routing
multiagenda/urls.py - Accounts and access
usuario/views.py - Professional management
profissional/views.py - Client management
cliente/views.py - Service management
servico/views.py - Appointment workflow
agendamento/views.py
Business domains
- Company records
empresa/models.py - User records
usuario/models.py - Professional records
profissional/models.py - Client records
cliente/models.py - Service records
servico/models.py - Appointment records
agendamento/models.py - Agenda slots
agenda/models.py - Image records
imagem/models.py
Persistence
- PostgreSQL
Other components
- Staff or client
Connections 23
- Staff or client → URL routing: opens
- URL routing → Accounts and access: routes requests
multiagenda/urls.py - URL routing → Professional management: routes requests
multiagenda/urls.py - URL routing → Client management: routes requests
multiagenda/urls.py - URL routing → Service management: routes requests
multiagenda/urls.py - URL routing → Appointment workflow: routes requests
multiagenda/urls.py - Accounts and access → PostgreSQL: queries and updates
usuario/views.py - Professional management → PostgreSQL: queries and updates
profissional/views.py - Client management → PostgreSQL: queries and updates
cliente/views.py - Service management → PostgreSQL: queries and updates
servico/views.py - Appointment workflow → PostgreSQL: reads and saves
agendamento/views.py - Professional management → Agenda slots: generates slots
profissional/views.py - Agenda slots → PostgreSQL: stores availability
- Company records → PostgreSQL: maps table
- User records → Company records: belongs to
usuario/models.py - Professional records → Company records: belongs to
profissional/models.py - Client records → Company records: belongs to
cliente/models.py - Service records → Company records: belongs to
servico/models.py - Appointment records → Service records: references service
agendamento/models.py - Appointment records → Client records: references client
agendamento/models.py - Agenda slots → Professional records: references professional
agenda/models.py - Agenda slots → Appointment records: references appointment
agenda/models.py - Image records → Client records: references client
imagem/models.py