WOW Outdoor App Admin Guide

When a User Qualifies

• User emails wowoutdoorapp@outlook.com stating their profile screen shows 100+ pts for the current month.
• Verify: Ask for a screenshot of their Profile screen showing the monthly VIP progress card with 100+ points.
• Check: Confirm they have not already earned 6 free months this calendar year, and have not exhausted the 5-year lifetime cap.
• Critical check: Confirm the user is NOT currently on an Annual Earned VIP year. Check vip_type in Supabase — if it is annual_earned and vip_expires_at is in the future, the monthly earn is paused for this account. Do not grant overlapping monthly VIP during an active Annual Earned VIP period.

How to Grant in Supabase

1. 1 Open Supabase Table Editor → profiles table.
2. 2 Find the user by email or username.
3. 3 Set vip_status = active
4. 4 Set vip_type = monthly_earned
5. 5 Set vip_expires_at = the last day of the next calendar month (e.g. if granting in April, set 2026-05-31T23:59:59Z).
6. 6 Save the record. The user's app will pick up the updated VIP status on next sync.
7. 7 Reply to the user confirming their VIP has been applied for the month of [month name].

Eligibility Checklist

• Active Cloud membership — confirm the user currently holds a Cloud (or higher) subscription. Check vip_status or subscription records. Free-plan users do not qualify. If they are on a paid VIP subscription, they also qualify (Cloud is the minimum).
• 1,000 total entries in a rolling 365-day window — includes fish, pots, wildlife, birds, hunting. GPS state bonus points count toward this. The 365-day window is rolling (any 365 consecutive days), not tied to the calendar year. Ask the user what their start date is and count entries from that date forward in Supabase.
• 150 wildlife sightings within the same 365-day window — count rows in wildlife_sightings + bird_sightings with created_at within the claimed window.
• 600 public hotspot posts within the same 365-day window — count rows in hotspots where user_id matches, visibility_scope != 'private', and created_at is within the window.
• Lifetime cap check — confirm this account has received fewer than 5 annual earned VIP years. Track in your admin log.
• Not already on Annual Earned VIP — confirm vip_expires_at is not already in the future for a previous annual_earned grant.

How to Grant in Supabase

1. 1 Open Supabase Table Editor → profiles table → find the user.
2. 2 Set vip_status = active
3. 3 Set vip_type = annual_earned
4. 4 Set vip_expires_at = exactly 365 days from today (e.g. if granting April 5 2026, set 2027-04-05T23:59:59Z).
5. 5 Save. Reply to user confirming 365-day VIP granted, starting today and expiring on [date].
6. 6 Inform the user: "During your VIP year, monthly VIP points will not accumulate. Your Lifetime VIP progress continues. When your year ends, you can immediately begin working toward your next Annual Earned VIP year."
7. 7 Increment the user's annual earned VIP year count in your admin records (to track the 5-lifetime cap).

Eligibility Requirements

• 10,000 total entries across all activity types. GPS state bonus counts toward this.
• 2,000 wildlife sightings (wildlife_sightings + bird_sightings tables combined).
• 8,000 public Network Hotspot posts.
• Pot events capped at 6,000 — only the first 6,000 pot records count toward the total. Pull the count from Supabase but apply the cap manually.
• Admin must verify at least 70% of entries as legitimate — review a sample across each activity type to confirm authentic GPS-logged entries. Spot check for duplicate or suspicious mass-entries.

Verification Procedure

1. 1 Request the user to email a full-screen profile screenshot showing all progress bars at 100%.
2. 2 Query Supabase to confirm exact counts for each activity table for that user's user_id.
3. 3 Sample at least 200 entries across all tables — check that GPS coordinates are geographically plausible, timestamps are spread over time, and entries are not duplicates.
4. 4 If 70%+ pass the plausibility check, proceed. If not, inform the user and specify which entry types failed review.
5. 5 In Supabase profiles table: Set vip_status = lifetime, vip_type = lifetime, clear vip_expires_at (set to null).
6. 6 Reply to user with confirmation. Lifetime VIP never expires and is not dependent on subscription renewal.

Key Database Fields — profiles Table

Useful SQL Queries

Run these in the Supabase SQL Editor:

• Find user by email:
  SELECT * FROM profiles WHERE email = 'user@example.com';
• Count all entries for a user:
  SELECT COUNT(*) FROM fish_catches WHERE user_id = 'UUID';
  Repeat for wildlife_sightings, bird_sightings, crab_pots, hunting_harvests.
• Count public hotspots:
  SELECT COUNT(*) FROM hotspots WHERE user_id = 'UUID' AND visibility_scope != 'private';
• List all active VIP users:
  SELECT username, email, vip_status, vip_type, vip_expires_at FROM profiles WHERE vip_status != 'none';

Supabase Access

• Dashboard: supabase.com/dashboard/project/itxxaaidtfiqzyrsfmvx
• Project ID: itxxaaidtfiqzyrsfmvx
• Service Role Key: stored as SUPABASE_SERVICE_ROLE_KEY environment secret in Replit.

Required for Every Feature Change

• User Guide (website/guide.html) — Update or add the relevant section covering the feature from the user's perspective. Include step-by-step instructions, screenshots descriptions, and tips where applicable.
• Admin Guide (website/admin-guide.html) — Update the relevant admin procedure, rules reference table, field list, or changelog entry. Any feature that changes admin workflows, VIP rules, database fields, or earn thresholds must be updated here.
• Changelog (Section 8 below) — Add a dated entry summarizing the change.
• replit.md — Update the project overview if architecture, key files, or major features change.