📧 Email Forwarding

💡 Why it makes the team better

A job alert that you configured is already filtered to what you want: the right role, the right city, the right seniority. When that alert lands in the team inbox, the Scouts get a pre-qualified lead instead of guessing keywords on the open web. Concretely:

• 🎯 Higher accuracy— the position matches your real intent (your alert filters), not a Scout's best guess.
• 💸 Less token waste — no broad web crawling, no fighting login walls. The Scout reads a link the platform already vetted for you.
• 🧩 More tailored over time— tune your alert filters and the team's input changes with you.
• 🌍 Any platform, not just LinkedIn — forward alerts from LinkedIn, Glassdoor, Indeed and any local/country/city-specific job board that emails you. If it sends a notification, the team can read it.

Every position the team creates is tagged with its source (e.g. linkedin-email vs a web search), so you can see on the dashboard how the email-sourced ones compare.

🗺️ The three steps

1. Create a dedicated inbox for the team   →  e.g. yourname.jht@gmail.com
2. Share it with the team (desktop app)    →  email + app-password, saved locally
3. Auto-forward your job alerts into it    →  from LinkedIn + any platform

1️⃣ Create a dedicated inbox

Make a fresh, separateemail address that the team will read — don't give it your personal inbox. A free Gmail account works well (the team defaults to imap.gmail.com). Keep it dedicated to job alerts only: everything that lands there is treated as a potential lead.

2️⃣ Share the inbox with the team (desktop app)

In the JHT desktop app, open Settings → Team email and enter:

The desktop app saves these locally (in the team's credentials/ folder on the machine that runs the team) — they are never sent to the cloud.

The "How to set up forwarding" button in that window brings you back to this guide.

3️⃣ Auto-forward your job alerts

This is the part that lives in your mailbox. You create rules that forward job-alert emails into the dedicated inbox. Set up as many sources as you like.

🔗 LinkedIn (most recommended)

1. Run the search you care about on LinkedIn (role, location, filters).
2. Save it as a Job Alert and set the frequency (daily is a good default).
3. Make sure email notifications are on for that alert (Settings → Communications → Email → Jobs).
4. In your personal mailbox, add a filter/rule: when the sender is jobs-listings@linkedin.com (or jobalerts-noreply@linkedin.com), forward to your dedicated team inbox.

📨 Gmail (forwarding rule)

1. Settings → Forwarding and POP/IMAP → Add a forwarding address → your team inbox, and confirm it.
2. Settings → Filters → Create a new filter → match the alert senders (e.g. from:(linkedin.com OR glassdoor.com OR indeed.com)), then Forward it to your team inbox.

📨 Outlook / others

Use Rules (Outlook) or your provider's equivalent: if sender contains the job-board domain → forward to the team inbox.

🌍 Any other platform (local / country / niche boards)

Same recipe for every site that emails you job notifications — national boards, city portals, niche communities. Subscribe to their alerts, then forward those emails to the team inbox. The team reads the whole dedicated inbox, so new platforms work without any extra configuration on the team side.

🤖 How the team uses it

• 🌅 Start of day — the Captain and the Scouts check the team inbox first thing in the working window, before any web search. Overnight alerts are already waiting.
• 🧮 The Captain balances the load — if a reasonable number of alerts arrived, the team reads them all (more signal is better). If a flood arrives (say hundreds in one day), the Captain picks the most salient ones and pushes those through, so the goal is always met: new positions reach a score, not just pile up un-scored.
• 📊 You see the result — the positions show up on your dashboard, scored, tagged with their email source.

✅ Verify it's working

After you've set up forwarding and entered the credentials, the team confirms access at the next start-of-day check. You can also watch your dashboard: within a working window you should start seeing positions whose source is an *-email tag.

If nothing shows up:

🔒 Privacy & security

• The credentials are stored locally, with the team — never uploaded to the cloud.
• Use a dedicated inbox and an app-specific password so the team never holds your personal mail or your real login.
• Revoke any time: delete the app password (the team simply stops reading) or change it in the desktop app.

🖼️ Graphic materials

This guide is user-facing but has no screenshots yet. Placeholders to fill in: