Feature · multi-tenant clinic config
Multi-tenant clinic config
Cada clínica config 100% independiente · 8 dimensiones (brand · servicios · horarios · staff · KB · compliance · branding · notifications) · 6 isolation guarantees database-level · 6 scalability design rules · zero cross-tenant leak tested rigorously.
8 config dimensions per-clinic
Brand voice + tono
Profesional · familiar · técnico · jovial · per-clinic configurable · system prompt customized · ejemplos provided
Servicios + pricing rangos
Catálogo servicios per-clinic · pricing rangos públicos opcional · privado por defecto · NO precios inventados bot output
Horarios atención
Horario clínica · disponibilidad respuestas vs handoff humano · weekends/festivos config · timezone Europe/Madrid default
Staff routing rules
Servicio → profesional específico · certifications · especialidades · multi-location support · fallback rules
Knowledge Base FAQ
FAQs clínica · políticas cancelación · ubicación · parking · cómo llegar · primeros pacientes flow · RAG retrieval queries
Compliance + claims
Forbidden claims per-vertical (dental · estética · psicología · etc) · per-vertical regulatory specifics · per-clinic disclaimers
Branding visual + logo
Logo clínica · colors brand · admin dashboard skin · widget chat embed branded · email signature personalized
Notification preferences
Slack · email · SMS founder · per-staff member · per-event-type · escalation rules differential
Isolation guarantees · 6 layers
- Database row-level security (RLS) Postgres enforces clinic_id boundary · zero trust application layer
- Per-tenant encryption keys pgsodium · PII columns encrypted con clinic-specific key derivation
- Per-tenant rate limits + quotas · noisy neighbor protection · cost-cap per-clinic
- Per-tenant audit logs · clinic admin sees only own logs · super admin solo founder · auditor solo anonimized
- Per-tenant config NOT shared · clinic A config NOT visible clinic B · API enforces tenant context every request
- Per-tenant backups · selective restore per-clinic · client-self-export per-tenant data portability GDPR Art 20
Scalability design · 6 reglas
Shared DB · per-tenant RLS · scales to ~1000 tenants single instance Supabase Pro · cost-efficient
Dedicated DB tier disponible Enterprise · post-tracción · custom contracts · 10x operational cost vs shared
Per-tenant scaling · vertical (more compute per clinic) automatic · horizontal (more clinics same infra) linear
Cross-region availability planned post-tracción · client-specific region requirement Enterprise · EU default current
Failover per-tenant · partial failure 1 tenant NOT affects others · isolated incident response
Multi-region tenant data residency · Enterprise option · contractual requirement Schrems II compliance
Config lifecycle · 6 fases
- Onboarding · Setup wizard founder + cliente · 8 dimensions configured 1-2h session
- Update self-service · clinic admin dashboard cambios common config without ticket
- Update assisted · cambios complex (brand voice retune · new vertical adoption) · 1:1 founder call
- Audit · Quarterly review per-clinic · founder + clinic admin · config drift identified
- Version control · todos cambios config versionados · rollback anywhere · audit trail completo
- Documentation · cada cambio config requires WHY note · prevent silent config drift
¿Tu DSO/cadena necesita multi-tenant management?
Para DSOs/cadenas dentales · multi-clinic dashboard unificado · cross-clinic analytics · shared services config templates · disponibles Enterprise tier.