Last updated: Aug 1, 2025, 02:40 PM UTC

Vercel Deployment Authentication Setup Guide

Your Deployed Site

Your test documentation site is now live at:

Step 1: Grant User Access for Vercel Domain

Since we now use domain-based authentication, you need to grant users access to the Vercel domain.

Option A: Using Supabase Dashboard (Recommended)

  1. Go to your Supabase project: https://supabase.com/dashboard/project/xcihhnfcitjrwbynxmka
  2. Click on Table Editor in the left sidebar
  3. Select the docbuilder_access table
  4. Click Insert row
  5. Add:
    • user_id: Select the test user from dropdown
    • domain: doc-builder-2znroyb5z-lindsay-1340s-projects.vercel.app
  6. Click Save

Option B: Using SQL Editor

  1. Go to your Supabase project dashboard
  2. Click on SQL Editor in the left sidebar
  3. Run this SQL command:
-- Grant user access to Vercel deployment domain
INSERT INTO docbuilder_access (user_id, domain)
VALUES (
  (SELECT id FROM auth.users WHERE email = 'testuser@example.com'),
  'doc-builder-2znroyb5z-lindsay-1340s-projects.vercel.app'
);

-- Verify the access
SELECT u.email, da.domain, da.created_at
FROM docbuilder_access da
JOIN auth.users u ON u.id = da.user_id
WHERE da.domain = 'doc-builder-2znroyb5z-lindsay-1340s-projects.vercel.app';

Step 2: Test Authentication Flow

Once the database is updated, test the authentication:

  1. Visit your site: https://doc-builder-2znroyb5z-lindsay-1340s-projects.vercel.app
  2. You should be automatically redirected to the login page
  3. Login with your test credentials:
    • Email: testuser@example.com
    • Password: testpass123
  4. After successful login, you should see the test documentation content

Step 3: Verify Authentication Features

What Should Work:

  • Automatic redirect to login for unauthenticated users
  • No content flash before redirect (fixed with CSS)
  • Successful login with valid credentials
  • Access to documentation after authentication
  • Logout functionality
  • Session persistence across page refreshes

Things to Check:

  1. Network Tab: Look for Supabase API calls to verify authentication
  2. Console: Check for any JavaScript errors
  3. Browser Cache: Clear cache if you see stale content
  4. Session Storage: Verify Supabase JWT token is stored

Troubleshooting

If Login Fails:

  • Verify the domain was updated correctly in Supabase
  • Check browser console for errors
  • Ensure cookies are enabled
  • Try incognito/private browsing mode

If Content Doesn't Show After Login:

  • Clear browser cache completely
  • Check console for JavaScript errors
  • Verify the authenticated class is added to body element
  • Ensure JavaScript is enabled

Next Steps

After successful testing, you can:

  1. Create Production Deployment:

    # Deploy to production URL
vercel --prod

  2. Add Custom Domain:

    • Configure custom domain in Vercel
    • Update Supabase database with new domain

  3. Add More Users:

    # Use CLI command
npx @knowcode/doc-builder auth:add-user production-email@example.com

  4. Deploy Multiple Sites:

    • Each site uses its domain for authentication
    • Users can have access to multiple domains
    • Central authentication system

Security Notes

  • The Supabase URL and anon key are public (by design)
  • Security is enforced through Row Level Security (RLS) policies
  • JWT tokens expire and auto-refresh
  • Password hashing is handled by Supabase (bcrypt)

Important URLs

Status: Ready for database update and testing
Next Action: Update the domain in Supabase database