JAIMZ GroupCompliance & MaintenancePortal
Not connected

Connect your Supabase project

The portal currently runs on fictional in-memory data. Follow these steps to connect your existing Supabase project when you are ready.

  1. 1

    Connect the Supabase integration

    In v0, open the settings menu (top right), choose Settings → Integrations and connect your existing Supabase project. This uses Vercel's managed connection, so no passwords need to be shared in chat.

  2. 2

    Confirm the public variables

    Only NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY (publishable key) are needed by the app. Check them under Vars in the settings menu.

  3. 3

    Review your schema together

    Once connected, ask v0 to read the live schema. Column names will be mapped to the demo data shapes and any missing tables (quotations, jobs, inspections, invoices) proposed for your approval.

  4. 4

    Enable Row Level Security

    Policies will restrict each role to its own records, for example tenants see only properties they are a member of through property_members.

  5. 5

    Switch on real sign-in and storage

    Supabase Auth replaces the demo role switcher, and a Supabase Storage bucket stores maintenance and before/after photos. Each step will be tested before it is described as working.

Your existing tables
How the demo maps to the tables you described. Column names will be confirmed against your live schema.

  • profiles User name, contact details and role (tenant, manager, landlord, admin).

  • agencies Real estate agencies serviced by JAIMZ Group.

  • agency_members Links property managers to their agency.

  • properties Rental properties, address and compliance dates.

  • property_members Links tenants, landlords and managers to properties.

  • maintenance_requests Tenant-reported issues, urgency, status and photos.

  • quotations Used by the demo; not in your current schema. Will be proposed as a migration.

  • jobs Used by the demo; not in your current schema. Will be proposed as a migration.

  • invoices Used by the demo; not in your current schema. Will be proposed as a migration.

Inspection and reporting storage
A proposed migration is included at supabase/migrations/20261021000000_inspection_module.sql. It has not been applied. Review its assumptions about your existing column names first.

  • inspections Header, attendance, scope, limitations, executive summary and inspector sign-off.

  • inspection_findings One row per checklist item: finding, observations, measurements, testing and structured defect fields.

  • inspection_photos Caption, annotations and storage path for each photo, linked to its finding and property.

  • inspection-photos (bucket) Private Storage bucket. Files are read through RLS-checked signed URLs, never public links.

Environment variables
Added automatically by the Supabase integration.
NEXT_PUBLIC_SUPABASE_URL=https://<project-ref>.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=<public anon key>