Latest eWorkConnection capabilities

Job Seeker Workspace

Job seekers use `/dashboard` to search jobs from enabled sources, compare match quality, prepare truthful application materials, and track applications.

• Loaded job results reset on a new search so old results do not stay mixed with the new search.
• Job matches default to highest match score first, with user sorting available for match, compensation, recency, company, location, and source when available.
• Company-posted jobs can appear in normal job seeker search only when the employer workspace is active, verified, public availability is enabled, and the job post is active and public.
• Resume and job matching should explain fit and gaps; generated resume or cover-letter changes must stay grounded in the uploaded resume and user-provided facts.
• Recruiter visibility is off by default. Job seekers must explicitly opt in before limited profile signals can be used for recruiter discovery.

Talent Hire And Recruiter Workspace

Recruiters use `/recruiter` for candidate discovery, company hiring leads, job posting, job description drafting, outreach, comparisons, and pipeline follow-up.

• Employer verification is admin-reviewed. Recruiters can submit company details, business email, and a public business profile, but they cannot self-approve verification.
• Active job posts require employer verification. Draft, active, paused, closed, and deleted states are supported.
• Job posts support full-time, part-time, contract, temporary, internship, remote, hybrid, onsite, compensation range, benefits, certifications, travel, visa, clearance, and other optional facts where the form provides them.
• AI-assisted job descriptions can help draft or refine posting language, but recruiters must confirm the recommendation before saving and should not invent facts.
• Pipeline and intro workflows are designed around consented job seekers and public professional information, with contact details limited by privacy rules.

Company Workspace

Admin And Super Admin Controls

• Admin user management includes role access, country scope, trial controls, job seeker recruiter-consent checkbox, employer verification status, and block/unblock actions.
• Promotion controls support default 0 percent selection, one active country/global promotion at a time, and super-admin user-specific promotions for selected users.
• Feature flags control registration requirements, recruiter launch, company workspace, homepage services, source visibility, maintenance, QA/dev workflow, and regulated sections.
• User Activity is expected to auto-load in Admin and summarize user activity, including total time spent where tracking data is available.
• The isolated `/page_ceo` demo page is controlled from Admin and can be enabled, disabled, and protected with an admin-managed passcode.

Staging And Production

Production uses the normal Vercel environment variables. Staging must use `NEXT_PUBLIC_EWC_ENV=staging` and `_STAGING` variable names so it never points at production by accident.

• Main branch remains production.
• Staging branch is for upcoming feature development and preview testing.
• Bug fixes that affect production should land on main and then be mirrored to staging.
• Staging Supabase, Stripe, Anthropic, Resend, and job-source keys should be separate where possible.
• Promotion from staging to production is a code merge/review process, not an in-app database variable switch.

Database Setup Required For Latest Features

The latest feature set needs the newest `lib/schema.sql` sections applied in Supabase before all controls work.

• User-specific promotions: `user_promotion_assignments`.
• Recruiter pipeline: `recruiter_pipeline_items` and `recruiter_pipeline_events`.
• Company workspace: `company_workspaces` and `company_workspace_members`.
• Feature flag seed: `company_workspace_enabled`.
• Profiles policy/trigger updates that prevent self-approval of recruiter verification.

Reference Links