Owner overview
Connected cemeteries
All cemeteries
Your Owner account can see its currently assigned cemeteries. Future customer onboarding will create isolated cemetery memberships and datasets.
| Cemetery | City | Public enabled | Management |
|---|
Customer onboarding
Cemetery onboarding tracker
Each customer has their own persistent checklist. Check an item when complete, then enter notes describing what was completed, files delivered, contacts, decisions, or follow-up work. Notes are saved to Supabase after editing.
Project checklist
Software usage
Activity leaderboard
Not yet measured
Not yet measured
Not yet measured
Additional metrics to enable
Owner Map Editor — Staging
Owner-only sandbox: Save new, moved, and archived points to a separate Owner table. Existing IOOF headstone coordinates and the public cemetery map are not modified by this editor.
Plot point editor
Turn Move Points ON, select a plot dot, then click a clear location for the destination. The selected point gets an outline. Shift-click a different dot to move to its location. Repeat until switching Move Points OFF. Original IOOF coordinates remain preserved.
Sign in and open this tab to work with Owner map points.
Stored Owner Points
Cemetery business operations
Track plans, customer status, renewals, storage, support, and next follow-ups for each cemetery. These are manually entered business metrics until integrations are configured.
Customer portfolio
| Cemetery | Customer status | Monthly fee | Renewal | Support items | Follow-up |
|---|
Customer fields are saved manually. Actual charges, storage-meter readings, and support tickets are not automatically connected yet.
Access & security
Owner access — verified against the Supabase legacy_owner_accounts table on sign-in.
Administrators — manage burial records and primary photos, not physical plot geometry.
Public — can view only approved public map records without signing in.
Recommended — enable MFA, audit owner map edits, and retain recoverable record archives.
Opening this dashboard does not itself establish map-editing RLS permissions.