DashboardSupportWelcome

👤 USER DOCS

Getting Started

Daily Operations

Shift Workspace & TasksPre-Shift SetupLine-Up CardsShift ReportsForms

Staff & Locations

Staff SchedulingManaging Locations

Oversight

Manager ReportsAnalyticsPre-Shift & Compliance

Incidents & Feedback

Incident ReportingAnonymous FeedbackMessages & Announcements

AI & Settings

AI ChatgearApp Settings

Administration

Dashboard & OnboardingAdmin

⚙️ DEVELOPER DOCS

Getting Started

Getting StartedDevelopmentDeployment Guide

Architecture

Architecture OverviewData FlowArchitecture Decision Records

Core Domain

Core DomainDatabase ReferenceLocations DomainAuth & RBACScheduling DomainReports DomainIncidents DomainNotifications DomainAudit Log & OptimizationDesign Audit Findings

Frontend

Frontend ArchitectureFormsLoading SkeletonsComponentsPWA & NotificationsimageScreenshots

API Reference

API Reference

Endpoints

POS Sales APIOptimization Data APISchedule Shifts APIEmployee Export APIReports APIIncidents APIAI Chat APIPush Notifications APIWebhooks APICron API

Contributing

ContributingcodeCode Examples

Security

Security & Compliance
Danvas IconDanvas
Danvas IconDanvas

Core Domain

Technical architecture and data models for Danvas domains

Overview

The Core Domain documentation provides deep technical insights into the architecture, data models, and automated workflows that power Danvas. This section is intended for engineers and contributors.

Domain Models

Database & Schema

Global schema overview and multi-tenant isolation patterns.

Locations

The hierarchy and data isolation of restaurant locations.

Scheduling

Technical design of the management shifts and tasks.

Reports

Deep dive into staff and manager report schemas.

Auth & Security

Clerk integration, middleware, and RBAC implementation.

Notifications

Push notifications, Slack routing, and Matrix bot.

Architecture Decision Records

Significant architectural decisions made during development

Database Reference

Overview of the database schema and data model

On this page

OverviewDomain ModelsTechnical PatternsRelated

Technical Patterns

  • Multi-tenancy: All data is scoped to a teamId (Clerk Organization).
  • Server Actions: Primary pattern for data mutation in the App Router.
  • Drizzle ORM: Used for all database interactions with strict typing.
  • Zod Validation: Validates all incoming data at the boundary.

Related

Architecture Overview

API Reference

Frontend Architecture