Skip to main content
Matching settings decide what Clustr counts as a path to someone: which kinds of evidence may show one, and what “small company”, “recent” and “same place” mean. There is one set per workspace. It applies everywhere at once: every table, Slack and webhook deliveries, the weekly digest, calendar briefings and Ask Clustr. Admins change them in the app under Settings > Matching, or with the update_matching_settings MCP tool. Everyone in the workspace can read them. Every change is logged with who made it and when, and any earlier version can be restored. A workspace that has never saved follows Clustr’s defaults, including any later change to a default. Once you save, your values stay yours.

What counts as a path

Five kinds of evidence. All are on by default. A path whose only evidence is a kind you switch off is not shown, and a switched-off kind never makes a path warm. Paths with no interaction and no recommendation are shown only in workspaces that include them, and only when the two worked together at a small enough employer in the same place. Switching off worked_together or same_place hides those paths.

Definitions

Client companies

hide_customers (on by default) hides people who work at one of your client companies everywhere Clustr shows paths. A saved view or a request can still show them: a request that names exclude_client_companies uses its own value, and one that names nothing follows this setting.

Reading and changing them

get_matching_settings returns the current settings, their version, whether the workspace has saved at all, and the defaults. update_matching_settings takes a config object with only the fields you want to change, and an optional reason kept in the log:
A value out of range is refused with every failing field named, and nothing is saved. Workspace admins only.

Overlap-only paths

A path whose only evidence is a shared employer or school (no interaction, recommendation or LinkedIn connection) is an overlap-only path. They are off by default for every workspace, and turning them on is a Clustr staff setting for now: ask us if you want them.
  • Off: Clustr does not store overlap-only paths for the workspace. A pair a person acted on (a note, a dismissal or other triage, an intro request, a tag or a hand-picked owner) is always kept, and a pair that gains an interaction, recommendation or connection gets its path. “Worked together” on a detail page is still shown. Counts, opportunities_count included, match what the lists show.
  • Turning on queues a build of the workspace’s overlap-only paths. The list fills in as it runs.
  • Turning off queues the removal of the stored ones. Nothing is removed until staff run it, and every removed row is archived first.