
When to create a collection
Create a collection when you need to:- track a set of people or accounts over time
- compare warm paths across a target list
- share a focused set with teammates
- revisit targets after new evidence arrives
- separate strategic lists from everyday contacts
What a collection shows
| Field | How to use it |
|---|---|
| Name | Keep the collection goal specific, such as Investors Q2 or Founding Engineer Targets. |
| Description | Explain why the collection exists and what belongs inside it. |
| People count | Use count to catch overbroad lists before they become noisy. |
| Owner | Know who maintains the list and who should resolve stale entries. |
| Last updated | Revisit older collections before acting on path recommendations. |
| Visibility | Confirm whether the collection is private, shared, or team-visible. |
Visibility modes
- Private: only you can see and manage the collection.
- Shared: selected teammates can view or collaborate.
- Team: the collection is part of the broader workspace operating rhythm.
Operating pattern
- Start from People or Companies search.
- Add promising results to a focused collection.
- Review connector quality before requesting intros.
- Remove stale or low-priority targets as goals change.
- Use collection updates as a signal for team coordination.

