docs(audiences): document Excluded people matching — LinkedIn URL or email only

docs/audiences.md

@@ -190,6 +190,14 @@ Clay syncs data from Google BigQuery on the following schedules:
 
 **Note:** A search import only populates field values for companies or people that are **new** to your Audience. Records already in your Audience from Salesforce, Snowflake, or another higher-priority source keep their existing field values — Clay's search data has lower precedence and will not overwrite them. To populate or update a field (such as Industry) on records that already exist in your Audience, bring the search results into a Clay table and use the `Upsert Audiences Record` action to push those values to matching records.
 
+**Excluding people (or companies) from your search**
+
+The search setup includes an **Excluded people** panel (or **Excluded companies** for a Find Companies search) where you can specify up to 3 audiences to suppress from the results. Clay filters out any result that matches a record in your exclusion audience before importing.
+
+**Exclusions match by LinkedIn URL or email only** — not by job title, name, or other fields. If a record in your exclusion audience has neither a LinkedIn URL nor an email, Clay cannot resolve it to a Clay person profile and that record will not be excluded from the search results. For example, an exclusion audience of "all Salesforce contacts with a title" will only suppress contacts who have a matching LinkedIn URL or email on their record in the exclusion audience.
+
+**Exclusions operate within Clay only.** The exclusion prevents matching records from being imported into your Audience — it does not affect CRM write-back. When Clay exports enriched records to Salesforce or another CRM, whether a duplicate is created is determined by your CRM's own deduplication and upsert rules, not by the Clay exclusion. To prevent duplicate records in Salesforce, configure matching and deduplication rules in Salesforce directly.
+
 ### Importing from CSV
 
 You can import a CSV file of people or companies as a one-time import into Audiences.

docs/find-people-overview.md

@@ -56,7 +56,7 @@ To add more profiles from the same search to an existing people table without cr
     -   **Locked after creation:** The filter type (Clay table vs. custom list), which table is linked, and — when using a custom list — the specific company identifiers entered cannot be changed once the source exists. This is what the "Can only be changed during source creation" tooltip means. If you need to target a different set of companies (for example, to correct a mistyped domain), create a new Find People source with the corrected identifiers. The linked Clay table's row contents are not frozen, however: adding or removing rows from the linked table is reflected each time the source runs. When re-run after new companies are added, the source searches across all companies currently in the table, not just the newly added ones.
     -   **Run settings:** The source runs **Manually** by default — adding new companies to the linked table does not automatically trigger a new run. To automatically pick up new companies on a recurring basis, click the source column header in your people table, expand **Run settings**, and switch from **Manually** to **On a schedule**. Choose a frequency (Daily is most common) and click **Save schedule**. You can also click **Run now** at any time for an immediate on-demand run.
     -   **Company identifier type:** The identifier in your linked table or custom list determines how companies are resolved. **Domains** (e.g., `acme.com`) match at the root-domain level — useful for broader coverage, but may return people from a parent company or other entities that share that domain. **Company profile URLs** from the professional network match the exact company page, limiting results to that specific entity. Company profile URLs return fewer but more precise results; domains return more but may include unintended companies.
--   **Exclude people:** Exclude up to 3 different sets of people from your search using Clay tables, CSVs, or manual lists. You can exclude up to 300,000 people total (100,000 per source). Exclusions match by individual professional profile URL — each row in your exclusion table must contain a person-level profile URL. Adding a company name, domain, or company page URL to the exclusion table will **not** suppress all people from that company.
+-   **Exclude people:** Exclude up to 3 different sets of people from your search using Clay tables, CSVs, or manual lists. You can exclude up to 300,000 people total (100,000 per source). Exclusions match by **LinkedIn URL or email** — each row in your exclusion table must contain a person-level LinkedIn URL or email address. Adding a company name, domain, company page URL, or job title to the exclusion table will **not** suppress those people from the results.
 
     **To exclude all people at a specific company**, use a post-import lookup instead: after importing your Find People results, add a **Lookup single row in other table** action that matches each person's company domain against your company blocklist. Set a run condition on downstream enrichments (for example, `{{Company Blocklist Lookup}} is not empty` → skip) to suppress anyone whose employer appears on your list. See [Excluding records during enrichment](finding-companies-and-people-in-clay.md#excluding-records-during-enrichment) for the full pattern.
 -   **Past experiences:** Enable the **Include past experiences** toggle to extend your company, job title, and experience description keyword filters to also match against a person's past roles — not just their current one.

docs/lookup-rows.md

@@ -130,7 +130,7 @@ When prospecting existing accounts, contacts can leave a company, change roles,
 
    Find People now only fires for accounts where you have fewer than 2 prospects on file. (Clay automatically ensures the lookup runs before this condition is evaluated — column order in the table does not matter.)
 
-3. To avoid returning contacts who are already in your prospects table, open the Find People source configuration and add your prospects table to the **Exclude people** filter. Exclusions match by individual professional profile URL, so your prospects table must contain a profile URL column for this to work. See [Find People in Clay](find-people-overview.md) for details.
+3. To avoid returning contacts who are already in your prospects table, open the Find People source configuration and add your prospects table to the **Exclude people** filter. Exclusions match by LinkedIn URL or email, so your prospects table must contain a LinkedIn URL or email column for this to work. See [Find People in Clay](find-people-overview.md) for details.
 
 4. Add a **Send Table Data → Send row for each item in a list** column and point it at your prospects table. Each contact returned by Find People becomes a new row in your prospects table, where they flow into your existing enrichment and sequencing workflow.