Super Garden & Yard

–

Customers

–

Jobs Today

–

Jobs This Week

–

Open Jobs

–

Workers

Today's Jobs

This Week

Open Jobs

0

🌿

No open jobs. Create one to get started.

Scheduled

0 ▾ expand

Pending — Revisit Required

0

Job Completed — Not Invoiced

0

Job Completed — Invoiced

0 ▾ expand

🔍

Viewing as:

👤

Admin PINs

Super Admin PIN

Current PIN hidden for security

Admin PIN

Worker PINs

Business Details

Business Name

Business Phone

Templates

Supabase Connection

Supabase Project URL

Supabase Anon Key

📋 Setup Instructions

1

Create a free Supabase account

Go to supabase.com → click "Start your project" → sign in with GitHub. It's 100% free to start.

2

Create a new project

Name it sgy-scheduler, choose a password, select region ap-southeast-2 (Sydney).

3

Create the database tables

Go to SQL Editor in your project and run this SQL:

create table customers (
  id uuid primary key default gen_random_uuid(),
  first_name text not null,
  last_name text not null,
  mobile text,
  email text,
  address text,
  suburb text,
  service_notes text,
  price_notes text,
  created_at timestamptz default now()
);

create table workers (
  id uuid primary key default gen_random_uuid(),
  name text not null,
  mobile text,
  role text default 'Crew', -- Head Gardener / Senior Crew / Crew / Consultant
  active boolean default true,
  created_at timestamptz default now()
);

create table jobs (
  id uuid primary key default gen_random_uuid(),
  customer_id uuid references customers(id) on delete cascade,
  service_type text not null,
  job_date date,
  time_start time,
  time_end time,
  hours_required numeric(4,2),
  worker_ids text[],
  recurrence text default 'once',
  notes text,
  address text,
  status text default 'scheduled',
  est_revenue numeric(10,2),
  actual_charge numeric(10,2),
  payment_type text default 'cash',
  invoiced boolean default false,
  created_at timestamptz default now()
);

4

Get your API keys

Go to Project Settings → API. Copy the Project URL and the anon public key. Paste them in the form above.

5

Enable public access (for now)

Go to Authentication → Policies. For each table (customers, workers, jobs), add a policy: Enable read and write for all users. You can add login later.

↑

Already have a database? Run this migration

If you created your jobs table before the financial features were added, run this in SQL Editor to add the missing columns:

-- Allow job_date to be null (open/unscheduled jobs)
alter table jobs alter column job_date drop not null;

-- Add new columns (safe to re-run)
alter table jobs
  add column if not exists address text,
  add column if not exists est_revenue numeric(10,2),
  add column if not exists actual_charge numeric(10,2),
  add column if not exists payment_type text default 'cash',
  add column if not exists invoiced boolean default false,
  add column if not exists completion_photo text,
  add column if not exists completed_at timestamptz,
  add column if not exists completed_by text,
  add column if not exists completion_notes text,
  add column if not exists invoice_number text,
  add column if not exists pending_reason text,
  add column if not exists completion_location text,
  add column if not exists recurrence_data jsonb,
  add column if not exists hours_required numeric(4,2);

-- Add company field to customers (safe to re-run)
alter table customers
  add column if not exists company text;

The if not exists makes it safe to run even if some columns already exist. The drop not null on job_date allows open (unscheduled) jobs with no date.

For photo uploads, optionally create a public Supabase Storage bucket named job-photos. Without it, photos are stored as base64 text in completion_photo.