Temple-owned records
Your institution owns its devotees, staff records, connected accounts and operating history.
Temple operations: evidence-led availability
21 workflows passed bounded authenticated production checks. This proves the named workflow, not adoption, delivery, settlement or general availability.
Your institution owns its devotees, staff records, connected accounts and operating history.
BookMyMandir takes 0% of offerings. It records temple workflows without becoming merchant of record.
A passed production check proves only the workflow and limits named in its acceptance evidence.
Working today
Each workflow below passed its own bounded harness together with authenticated workspace bootstrap. Exact limits remain part of the release evidence; the list does not imply broad customer use.
For Temple admin, relationship staff · People records, consent, and acquisition
For Temple admin, data operator · People records, consent, and acquisition
For Comms staff, relationship staff · People records, consent, and acquisition
For Trustee, fundraiser · People records, consent, and acquisition
For Temple claimant, BMM ops · People records, consent, and acquisition
For Comms staff, language editor · Communications and campaigns
For Temple admin, seva office · Listings, bookings, darshan, and sevas
For Seva office, devotee · Listings, bookings, darshan, and sevas
For Priest, seva office, devotee · Listings, bookings, darshan, and sevas
For Gate staff, operations · Listings, bookings, darshan, and sevas
For Trustee, devotee · Offerings, donations, hundi, and receipts
For Trustee, cashier, accountant · Offerings, donations, hundi, and receipts
For Cashier, accountant, trustee · Offerings, donations, hundi, and receipts
For Temple admin, devotee · Presence, content, ads, and connected accounts
For Temple user, BMM ops · People, workforce, service desk, projects, and knowledge
For Owner, all staff · Tenant, governance, access, and platform
For Owner, auditor · Tenant, governance, access, and platform
For Devotee, data steward · DPDP, privacy, and legal operations
For Owner, manager · Analytics, reporting, and forms
For Trustee, fundraiser · Analytics, reporting, and forms
For Temple admin, seva desk · Analytics, reporting, and forms
Controlled beta: 1 workflow
Preview, consent checks and durable workflow controls exist. Current production holds campaign delivery until the owner configures signed Resend outcome authority. No provider request, inbox delivery, bounce or complaint result is claimed.
These names communicate direction, not current staff access. Source-complete work still needs authenticated production acceptance; foundation and planned work are earlier.
The implementation exists in source, but the named workflow does not yet have authenticated production evidence.
A technical foundation exists, but it is not a staff-ready workflow.
The workflow is part of the product direction; no staff workflow exists today.
Start with an operating need