Signing in
The seeded admin account, the sign-in routes, and reaching the two surfaces.
The seeded admin
Running the seed creates a platform-admin user you can sign in with immediately:
pnpm --filter @repo/scripts seed:e2e| Field | Value |
|---|---|
e2e-admin@nia.local | |
| Password | E2ePassw0rd!nia |
| Global role | admin (platform operator) |
| Organization | E2E Test Fund (slug e2e-test-fund, plan full), as owner |
The credentials can be overridden with the E2E_TEST_EMAIL and E2E_TEST_PASSWORD environment
variables before running the seed. The seed is idempotent: re-running it will not reset an existing
user's password or duplicate the organization.
Sign-in routes
Authentication lives under the unauthenticated route group of the saas app:
| Route | Purpose |
|---|---|
/login | Email + password sign-in. |
/forgot-password, /reset-password | Password reset flow. |
/verify | Email verification. |
/signup | Account creation. Disabled by default; the platform is invitation-only. |
Self-serve signup is turned off (enableSignup: false); new users join through an invitation to an
organization. Magic links, passkeys, and two-factor are also available depending on
configuration. See Authentication & multi-tenancy for the full
auth model.
Reaching the two surfaces
Because the seeded user is both a platform admin and an owner of a fund organization, you can reach both surfaces:
- Command Center: visit
/operator. Access requires the globaladminrole; non-admins are redirected away. - GP workspace: visit
/or the organization's path (/e2e-test-fund). This is the per-fund workspace any organization member sees.
To explore the platform as a non-admin GP user, invite a second user into the organization from Settings → Members and sign in as them.