Introduction
Venue
Private Worker for organisation-scoped venue operations: locations, people, checklists, tasks, exceptions, temperatures, and audit.
Maya Hospitality (web and app) calls /venue/* on the public API gateway. The gateway forwards to this Worker over the VENUE binding.
User types: admin, area-manager, manager, member (from Directory memberships on service venue). Garage roles on garage-crm map onto those types. Directory login omits actorType. Built-in permissions are defined in code; custom roles live in D1. Checklist photos and signatures are stored in R2 (MEDIA).
Bootstrap
Create brands with POST /v1/brands and venues with POST /v1/venues. locationId is the venue id. managerId and exception ticketId are opaque ids from the calling site. This service does not ingest a directory or call other APIs. Web login Turnstile is verified on the gateway before requests reach this Worker.
Health: GET /health and GET /v1/health.
Access roles
Built-in user types are fixed in code and listed by GET /v1/roles for the UI. Custom roles are stored in D1 and managed by admins.
| Display name | User type |
|---|---|
| Admin | admin |
| Area Manager | area-manager |
| Manager | manager |
| Member | member |
See the Venue API reference.