ARK

Verify Your Deployment

A short checklist to confirm everything is wired up correctly. If all of these pass, your deployment is healthy.

Checklist

Run through these in order. Each one takes seconds.

1. The site loads

Open your Vercel URL. You should see the login screen.

  • ✅ Yes — move to step 2.
  • ❌ Blank page or error — see Site won't load.

2. You can sign up and log in

Create an account (or log in if you already created one). Confirm the email link, then return to the site.

3. The admin menu appears

If you're the first user, you should see admin-only options (Settings, Team, Admin, etc.) in the navigation.

  • ✅ Admin items visible — move to step 4.
  • ❌ No admin items — see I'm not the admin.

4. You can create the first piece of content

Try creating a board (Track), channel (Comms), standup (Pulse), or space (Ink).

5. Refreshing the page keeps you logged in

Hit refresh.

6. The license key validates

Open your browser's developer tools (F12 or right-click → Inspect), go to the Network tab, and reload the page. Look for a request to arkteams.io/api/license/validate.

  • ✅ 200 response with { "valid": true, "reason": "active" } — you're done. Everything works.
  • ❌ Response says domain_mismatch — see License domain mismatch.
  • ❌ Response says not_found or revoked — see License invalid.
  • ❌ No request appears — the product may not have license validation enabled in dev. Try in production. If it still doesn't appear, email support.

If steps 1–6 all pass, your deployment is healthy. You can stop here.

Common issues and fixes

Site won't load

Most likely cause: the build failed in Vercel.

  1. Vercel → your project → Deployments.
  2. Find the most recent deployment. If it has a red ✗, click it and read the Build Logs.
  3. The first red error line tells you what's wrong. Most often:
    • Missing environment variable → add it under Settings → Environment Variables, then redeploy.
    • Typo in environment variable → fix and redeploy.
    • Build crashed in code → unusual on a fresh ARK install. Email support@arkteams.io with the build log.

Auth emails not arriving

  1. Check spam.
  2. Supabase → Authentication → Logs. Confirm the email was sent. If you see it logged but it never arrived, the recipient address may be on a Supabase-blocked list (rare). Try a different email.
  3. Supabase free tier rate-limits auth emails to 4/hour. If you've tried multiple signups quickly, wait an hour or set up your own SMTP under Authentication → Email Templates → SMTP Settings.

Email links go to localhost

You forgot to set the Site URL in Supabase.

  1. Supabase → Project Settings → Authentication → URL Configuration.
  2. Site URL: set to your Vercel URL (e.g., https://my-crm.vercel.app).
  3. Redirect URLs: add https://my-crm.vercel.app/**.
  4. Save.
  5. Send yourself a fresh password reset or confirmation. The new email will use the correct URL.

I'm not the admin

If someone else signed up first, they got the admin role.

  1. Supabase → Table Editor → profiles table.
  2. Find your row.
  3. Change role from member (or whatever the default is) to admin.
  4. Save.
  5. Log out and back in. Admin items will now appear.

Saves fail with a database error

Most likely cause: the schema didn't fully run.

  1. Supabase → Table Editor. Confirm the product's tables exist.
  2. If a table is missing, re-run the schema (see Running the Database Schema).
  3. If all tables exist but saves still fail, open the browser developer tools → Console tab. The error message usually points to the specific table or column that's missing or misconfigured. Email support with the error.

Session not persisting

Most likely cause: the Supabase URL or anon key in Vercel doesn't match the project you created tables in.

  1. Vercel → Settings → Environment Variables.
  2. Confirm VITE_SUPABASE_URL exactly matches Supabase → Project Settings → API → Project URL.
  3. Confirm VITE_SUPABASE_ANON_KEY matches the anon public key.
  4. If you fix anything, redeploy.

License domain mismatch

Your license is bound to a different domain. This happens if you:

  • Visited your *.vercel.app URL first, then added a custom domain
  • Copied the license key into a different deployment

To request a domain change:

  1. Go to arkteams.io/dashboard/products.
  2. Find the affected product.
  3. Click Change domain and enter your new production URL.
  4. Confirm.

You have 2 domain changes per rolling year. Use them carefully.

License invalid

  • not_found — typo in the license key. Compare it to your purchase email or your dashboard. The format is ARK-XXXX-XXXX-XXXX-XXXX (uppercase, with hyphens, no spaces).
  • revoked — the license has been revoked, usually due to a refund or a Terms of Service violation. Email support@arkteams.io if you think this is an error.
  • wrong_product — you're using a Track license on Comms (or similar). Each license is product-specific. Use the right one.

Still stuck?

Email support@arkteams.io with:

  • Your live URL
  • The product you're installing
  • The exact error message (copy/paste, not a screenshot)
  • The Vercel build log if the deploy is failing

Subscribers get priority response. Include your dashboard email so we can look up your account.