Operating Dashboard
Hybrid SaaS dashboard for local business operations
› Screenshots
3 planned
[ preview ]
Controlled mock preview of the operational administration control board.
Controlled mock preview of the operational administration control board.
Dashboard overview with sanitized tenant data.
· coming soon ·Lead/booking workflow.
· coming soon ·› Technical Stack
› Architecture Pipeline
› The Problem
PertoDaqui needs an operational back office, not just public pages. Each client has leads, bookings, staff, restricted areas, audit requirements and settings that must stay isolated per business.
› What I Built
I built the operating dashboard as the control layer of the platform: authentication, roles, site-scoped data, leads, booking settings, client areas, audit events and module configuration in one place.
› Core Capabilities
- Site-scoped dashboard areas for each business.
- Lead, quote and booking workflows tied to operational records.
- Role-based access with protected sessions and audit trails.
- Module switches for bookings, CRM, WhatsApp, client portal and AI features.
- Hybrid deployment path for sensitive data or client-owned infrastructure.
› Technical Decisions
Put site_id and role context at the center of the data model to avoid cross-client leakage.
Kept modules separate so bookings, leads, WhatsApp and AI can evolve independently.
Used audit logs for login, settings and operational changes that matter in production.
Kept Cloudflare as the default runtime while preserving Docker/VPS options for stricter workloads.
› What This Demonstrates
Multi-tenant product engineering: secure dashboard design, operational workflows, modular SaaS thinking, auditability and practical deployment tradeoffs.
› Limitations & Next Steps
- Tighten cross-environment migration tooling for client-specific deployments.
- Add a safer visual theme editor for client dashboards.