Allow Multiple Accounts for Different Orgs

[Indy1131]

Closes #73

• Created playwright test to model functionality
• Changed schema to integrate new functionality
• Updated BetterAuth's hooks to accomodate change

Checklist:

• I have mentioned a ticket above
• My changes meet the acceptance criteria of said ticket
• I have self-reviewed my changes
• I have requested a review from the appropriate team member(s)
• I have fixed all merge conflicts
• I have ensured CI checks pass

[netlify]

✅ Deploy Preview for servicestart ready!

Name	Link
🔨 Latest commit	59766d8
🔍 Latest deploy log	https://app.netlify.com/projects/servicestart/deploys/69e2691df3383b00082e1049
😎 Deploy Preview	https://deploy-preview-220--servicestart.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[greptile-apps]

Greptile Summary

This PR scopes user identity per-organization so the same email address can hold accounts across multiple orgs. It replaces the global findByEmail lookup with findByEmailAndOrganization, wires BetterAuth's adapter overrides (createUserOverride, findUserByEmailOverride) into a before hook, adds organization_id to the users table, and ships a new E2E test that verifies cross-org signup.

Several previously-flagged issues remain open (missing UNIQUE (email, organization_id) DB constraint, dead-code after hook path guard, ROOT_DOMAIN defaulting to lvh.me, userOrganizations absent from the schema export). The new migration also has no UPDATE statement to backfill organization_id for existing rows, which will silently break sign-in for any pre-existing user after the migration is applied.

Confidence Score: 3/5

Not safe to merge until the migration data-gap is addressed and previously flagged issues are resolved.

A P1 migration issue is introduced in this PR (no backfill for existing users, breaking sign-in post-upgrade). Multiple P1 findings from previous review rounds are still open: missing UNIQUE constraint, dead-code after-hook, wrong ROOT_DOMAIN default, missing schema export.

drizzle/20260417115347_broad_iron_patriot/migration.sql, lib/utils.ts, lib/auth.ts, lib/schema.ts

Important Files Changed

Filename	Overview
drizzle/20260417115347_broad_iron_patriot/migration.sql	Creates user_organizations table and adds organization_id to users. Missing UNIQUE constraint (previously flagged) and missing data migration for existing users with NULL org_id.
lib/auth.ts	Adds multi-tenant before hook with adapter overrides. after hook dead-code path guard unresolved.
lib/schema.ts	userOrganizations still absent from the schema export; otherwise schema changes are correct.
lib/authUtils.ts	New createUserOverride/findUserByEmailOverride logic is correct for new users.
lib/services/UserService.ts	Org-scoped lookup added; import { and } misplaced after function definition.
tests/e2e/multipleAccounts.spec.ts	Valid E2E test; name splitting via hardcoded offsets is fragile.
lib/utils.ts	ROOT_DOMAIN defaults to lvh.me — previously flagged, unresolved.

_{Reviews (8): Last reviewed commit: "Generate new migrations" | Re-trigger Greptile}

[greptile-apps]

Composite UNIQUE constraint missing from migration

The schema defines (table) => [sql\UNIQUE (email, organization_id)`]on theuserstable, but this migration only drops the oldusers_email_keyconstraint without adding the replacement composite one. Drizzle does not auto-generateALTER TABLE ADD CONSTRAINT` for raw-SQL constraints in migrations.

As a result, the database has no enforcement for the (email, org) uniqueness invariant. The application-level findByEmailAndOrganization check avoids duplicates most of the time, but concurrent sign-ups with the same credentials can still produce duplicate rows.

Add to the migration:

ALTER TABLE "users" ADD CONSTRAINT "users_email_organization_id_key" UNIQUE ("email", "organization_id");

[renatodellosso]

Overall flow looks good, but the PR needs some cleanup.

[renatodellosso]

Out of curiosity, what is "lvh.me"?

[Indy1131]

It's a domain that always resolves to the localhost. I was using it for the e2e testing for the different subdomains for each organization (a.lvh.me and b.lvh.me)

[renatodellosso]

Ah ok.

[renatodellosso]

@Indy1131 Once you restore the old migrations, we can merge this PR.

[greptile-apps]

No data migration for pre-existing users

After ADD COLUMN "organization_id" text, every row already in users will have organization_id = NULL. The new findByEmailAndOrganization query filters with eq(users.organizationId, organizationId), which never matches NULL, so any existing user who tries to sign in will be silently treated as non-existent and either receive a credentials error or generate a duplicate account.

Add a UPDATE statement to assign existing users to their organization before the column is used, e.g.:

UPDATE "users"
SET "organization_id" = (
  SELECT "id" FROM "organizations" ORDER BY "created_at" LIMIT 1
)
WHERE "organization_id" IS NULL;

Adjust the sub-query to match however existing users should be mapped (by slug, by the default org, etc.).