> ## Documentation Index
> Fetch the complete documentation index at: https://f4c7a9e2d8b1-docs.tenzo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Whitridge TargetRecruit sourcing fields

> Sourcing filter scope for Whitridge candidate fields synchronized from Salesforce

## Supported sourcing filters

Whitridge candidate sync maps these TargetRecruit fields from Salesforce into tenant-scoped typed sourcing attributes:

| Salesforce field              | Sourcing label     | Local key                          | Type          |
| ----------------------------- | ------------------ | ---------------------------------- | ------------- |
| `Last_Note_Date__c`           | Last Activity Date | `targetrecruit_last_activity_date` | Date          |
| `AVTRRT__Candidate_Status__c` | Candidate Status   | `targetrecruit_candidate_status`   | Single-select |
| `AVTRRT__Work_Status__c`      | Work Status        | `targetrecruit_work_status`        | Single-select |
| `CreatedBy.Name`              | Created By         | `targetrecruit_created_by`         | Single-select |
| `CreatedDate`                 | Date Created       | `targetrecruit_created_date`       | Date          |

Both date fields become available in the existing sourcing filter drawer after their values have synchronized.

* Last Activity Date and Date Created use an inclusive calendar date range. Salesforce datetime values are converted to Whitridge's `America/New_York` timezone before the calendar date is stored.
* Candidate Status, Work Status, and Created By use the existing include or exclude control. Options come from values currently synchronized on candidates, including historical values that are no longer active Salesforce picklist options.
* Created By is the Salesforce `CreatedById` relationship. Tenzo stores `CreatedBy.Name` so recruiters can filter by the creating user's name rather than the Salesforce user id.

Filters use values stored in Tenzo and do not query Salesforce during each search. Positive filters are strict, so candidates without a synchronized value for the selected field do not match.

## Scope boundaries

This delivery does not add sorting, natural-language filter inference, Salesforce write-back, or support for arbitrary TargetRecruit custom fields. It also does not change Tenzo's separate Last Note Date filter, which is based on synchronized candidate notes rather than `Last_Note_Date__c`.

## Deployment and backfill

Deploy the ongoing sync code before running the one-time Whitridge backfill. Run the backfill without `--apply` first and review its anonymous totals and incomplete-candidate count. Run `--apply` only after the dry run has been approved.