New sources
Map a new Slack channel, repo, or recurring meeting to a client and project in one place, so your time attributes itself.
As you work, ProjectPacer notices new things worth attributing: a Slack channel you've started posting in, a GitHub repo you've been committing to, a meeting that now repeats. New sources gathers the ones that aren't mapped to a project yet, so you can point each at a client and project once and have everything from it attribute itself after that.
Where to find it
On the AI Suggestions page, a New sources button sits next to the List and Timeline switch whenever there's something to map, with a count beside it. Click it to open the New sources screen. It takes over the page while it's open; click List or Timeline, or the New sources button again, to go back to where you were.
What it surfaces
Each card leads with the thing's own name, so you can tell at a glance what you're mapping:
- Recurring meeting (needs a calendar). A repeating series that isn't pinned to a project yet.
- New Slack channel (needs Slack). A channel you've posted in lately that isn't mapped.
- New GitHub repo (needs GitHub). A repo you've been active in that isn't linked to a project.
- Travel locations (needs the Travel & mileage suggestion). You tracked an in-person meeting but haven't saved a location to measure drives from. Unlike the others, this one lets you add a location right here rather than mapping to a project; once you've saved one, ProjectPacer can suggest the drive for meetings like it.
A source shows up here only once its integration is connected and its signal is on in Settings → AI suggestions. No Slack means no Slack channels here, and the same goes for GitHub and your calendar. Connecting alone isn't enough; nothing is read from a source until you switch it on.
Only what you're actually using
New sources shows only things you've been active in recently, not everything that exists. A channel you posted in this week appears; a repo nobody has touched in a while does not. That keeps the list short and worth acting on, and anything that goes quiet drops off on its own.
Map it, or ignore it
Each card gives you one decision:
Pick the project it belongs to (the picker spans every workspace, grouped by client). From then on it's linked, and future activity attributes to that project for you. The card leaves the screen. (The Travel locations nudge is the exception: instead of a project picker it shows Add a location, which opens a small label-and-address form right on the card — save it without leaving the page, and the travel suggestions take over.)
Not something you track? Ignore hides it. It won't come back to New sources, but it isn't gone for good; you can restore it later.
An ignored item stays discoverable in its source's own settings, each with a Restore:
- Recurring meeting: Settings → Calendar & travel, in the recurring rules (turn on "Show archived").
- Slack channel: Settings → Apps & integrations → Slack, marked "hidden from New sources."
- GitHub repo: Settings → Apps & integrations → GitHub, under "Hidden from New sources."
Ignoring the Travel locations nudge simply dismisses it — there's nothing to restore, since saving a location at any time replaces the nudge with the real travel suggestions.
A nudge, never a to-do
New sources stays out of your review count and never mixes into the suggestion list. It's a quiet prompt to finish a mapping, not another task on the pile. Mapping something here is the same as setting a rule in Settings, just closer to where you noticed it. For the full rules view and how matches are decided, see Mapping meetings to projects.
Once your sources map, review and log the time they bring in.