docs: add setup wizard email confirmation step

ysamcode · cursoragent · ysamcode · commit 70f1c3ea99de · 2026-02-25T09:08:28.000+01:00
The setup wizard now verifies that Supabase's "Confirm email" setting
is disabled before allowing admin account creation. Document this new
step in installation, configuration, and deployment pages.

Co-authored-by: Cursor &lt;cursoragent@cursor.com&gt;
diff --git a/content/deployment/index.mdx b/content/deployment/index.mdx
@@ -17,6 +17,7 @@ New Open Source installations use a setup wizard at `/ycode/welcome`. The wizard
 
 - Connecting to Supabase
 - Running database migrations
+- Verifying that the **Confirm email** setting is disabled in Supabase
 - Creating your admin account
 
 Complete the wizard before publishing.
diff --git a/content/getting-started/configuration.mdx b/content/getting-started/configuration.mdx
@@ -59,14 +59,23 @@ postgresql://postgres.[PROJECT-ID]:[PASSWORD]@aws-x-xx-xxxx-x.pooler.supabase.co
 
 Use the **Transaction Pooler** connection method, not the direct connection. The pooler runs on port 6543 and is required for serverless environments like Vercel.
 
+### Disable email confirmation
+
+Ycode manages its own authentication flow and does not use Supabase's email confirmation. You need to disable it before running the setup wizard.
+
+1. In your Supabase project, go to **Authentication > Sign In / Providers**.
+2. Find the **Confirm email** toggle and disable it.
+
+The setup wizard verifies this setting automatically. If email confirmation is still enabled, the wizard prompts you to disable it before you can create an admin account.
+
 ## Database Migrations
 
 Ycode uses migrations to create and update database tables. You can run them in two ways.
 
 ### Via setup wizard (recommended)
 
 1. Visit `/ycode/welcome` on your site.
-2. Complete the setup wizard. It creates your admin account and runs migrations automatically.
+2. Complete the setup wizard. It connects to Supabase, runs migrations, verifies the email confirmation setting, and creates your admin account.
 
 ### Via CLI
 
diff --git a/content/getting-started/installation.mdx b/content/getting-started/installation.mdx
@@ -42,6 +42,7 @@ Fork the [Ycode repository](https://github.com/ycode/ycode) on GitHub. This crea
    - `anon` public key
    - `service_role` secret key
 4. Go to **Settings > Database** and copy the connection string. Use the **Transaction Pooler** connection method (port 6543).
+5. Go to **Authentication > Sign In / Providers** and disable the **Confirm email** toggle. The setup wizard verifies this setting before allowing you to create an admin account.
 
 ### Step 4: Add environment variables in Vercel
 
@@ -60,8 +61,10 @@ Trigger a new deployment so Vercel picks up the environment variables. Use **Dep
 
 1. Visit your deployed site.
 2. Go to `/ycode/welcome` (e.g. `https://your-project.vercel.app/ycode/welcome`).
-3. Follow the setup wizard to create your admin account and run database migrations.
-4. When done, you can open the editor at `/ycode`.
+3. Follow the setup wizard to connect Supabase and run database migrations.
+4. Confirm that the **Confirm email** setting is disabled when prompted. The wizard checks this automatically.
+5. Create your admin account.
+6. When done, you can open the editor at `/ycode`.
 
 </Steps>
 
@@ -101,8 +104,10 @@ npm run dev
 ### Step 6: Run the setup wizard
 
 1. Open `http://localhost:3002/ycode/welcome` in your browser.
-2. Follow the setup wizard to create your admin account and run migrations.
-3. When done, open the editor at `http://localhost:3002/ycode`.
+2. Follow the setup wizard to connect Supabase and run migrations.
+3. Confirm that the **Confirm email** setting is disabled when prompted.
+4. Create your admin account.
+5. When done, open the editor at `http://localhost:3002/ycode`.
 
 </Steps>
 
