Digital Growth Force

Default sign-in (development)

In production, the seed password comes from the SEED_ADMIN_PASSWORD environment variable instead of the dev default.

Run locally

1. 1

   Start PostgreSQL

   Ensure PostgreSQL is running and the jazz_dgf database exists (Docker or local install).

   # Example with Docker
   docker compose up -d postgres

2. 2

   Configure & start the API

   Backend lives in d:\Jazz\backend (NestJS). Copy .env and run migrations + seed.

   • API base URL: http://localhost:3001/api/v1
   • Swagger docs: http://localhost:3001/api/docs
   • Set CORS_ORIGIN=http://localhost:3000 in backend .env

   cd backend
   npm install
   npx prisma migrate deploy
   npx prisma db seed
   npm run start:dev

3. 3

   Configure & start the frontend

   Next.js app in d:\Jazz\frontend. Point it at the API.

   • Frontend URL: http://localhost:3000
   • NEXT_PUBLIC_API_URL=http://localhost:3001/api/v1

   cd frontend
   cp .env.local.example .env.local
   npm install
   npm run dev

4. 4

   Sign in as Super Admin

   Open the login page and use the seeded admin credentials below. You will land on the Admin portal.

   Open login

Portal access rules

• Each user has exactly one sign-in portal: Field Sales, Sales Management, Leadership Insights, or Platform Administration.
• Portal is set automatically from the user's role — you pick the role when creating a user, not the portal separately.
• After login, users are redirected to their assigned portal only.
• Cross-portal URLs are blocked — e.g. an admin cannot open /edo even with a direct link.
• Permissions still control which screens and actions appear inside a portal.

Seeded roles vs user accounts

Roles and permissions are seeded automatically. User accounts for each role are not — you must create them.

Regional manager vs line manager (production)

Line manager and regional manager are two different ways to scope Sales Management data. They can coexist or work independently.

How to add a new user

Follow this flow to onboard EDOs, managers, executives, or additional admins.

1. 1

   Sign in as Super Admin

   Only users with users.create permission (Super Admin or scoped managers) can add accounts.

   Admin → Users
2. 2

   Open New User

   Go to Admin → Users → New User (/admin/users/new).

   Create user form
3. 3

   Fill required fields

   Provide identity and role — portal is derived automatically from the role.

   • Role — pick first (EDO, Line Manager, Regional Manager, etc.); this sets permissions and sign-in portal
   • Full name — display name across the platform
   • Email — used for login (required for invite flow)
   • Region — required for EDO; recommended for managers. Used for regional dashboards
   • Line manager — optional for EDO. Leave empty when EDOs report only at region level
   • Sales ID — optional EDO identifier (edoProfile)
   • Regional Manager — after create, assign region(s) in Admin → Organization
4. 4

   Save and send invite email

   On success, Resend emails the invite link to the user's address (when RESEND_API_KEY is configured). The invite token is also returned once in the API response as a backup.

   • User status becomes PENDING_INVITE until password is set
   • Invite links expire after 7 days
   • Without Resend configured, copy the link from Admin → Users → New User success screen
5. 5

   User opens email and sets password

   The email contains a button linking to /login/setup?token=…. After setting a password, the user signs in at /login.

   Invite setup page

Recommended test accounts

Create these manually to exercise each portal end-to-end.

What is live vs planned

Environment variables

Frequently asked questions