caricamentoโฆ
caricamentoโฆ
Feed the team your job alerts
Give the team a dedicated email address and auto-forward your job-alert notifications to it. The Captain and the Scouts read that inbox at the start of every working day and turn the alerts into scored positions โ without getting lost on the open web.
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:
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.
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 platformMake 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.
In the JHT desktop app, open Settings โ Team email and enter:
| Field | What to put |
|---|---|
| Email address | the dedicated inbox, e.g. yourname.jht@gmail.com |
| App password | an app-specific password, not your login password |
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.
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.
jobs-listings@linkedin.com (or jobalerts-noreply@linkedin.com), forward to your dedicated team inbox.from:(linkedin.com OR glassdoor.com OR indeed.com)), then Forward it to your team inbox.Use Rules (Outlook) or your provider's equivalent: if sender contains the job-board domain โ forward to the team inbox.
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.
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:
| Symptom | Likely cause | Fix |
|---|---|---|
No *-email positions appear | credentials not saved / wrong | re-enter email + app password in the desktop app |
| "Login failed" in the team logs | using login password, not app password | create an app-specific password and use that |
| Alerts arrive but aren't forwarded | mailbox rule not matching | check the sender address in your forwarding filter |
| Inbox empty | alerts not enabled at the source | turn on email notifications for your LinkedIn/board alerts |
This guide is user-facing but has no screenshots yet. Placeholders to fill in:
| # | Expected screenshot | Target path |
|---|---|---|
| 1 | Desktop Settings โ Team emailform (email + app-password + "How to set up forwarding" button) | docs/guides/assets/email-01-desktop-form.png |
| 2 | Gmail App password creation screen | docs/guides/assets/email-02-app-password.png |
| 3 | LinkedIn Job Alert with email notifications on | docs/guides/assets/email-03-linkedin-alert.png |
| 4 | Gmail forwarding filter forwarding alerts to the team inbox | docs/guides/assets/email-04-gmail-filter.png |
| 5 | Dashboard showing positions tagged with an *-email source | docs/guides/assets/email-05-dashboard-source.png |