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

# Ashby custom field mapping

> Map Ashby custom fields to ClearOffer fields to automatically populate your offers.

Use custom field mapping to translate your Ashby `Offer` custom fields into ClearOffer fields. When an offer is created or updated in Ashby, ClearOffer will fill in matching fields automatically.

<Info>
  Mappings only apply to offers that were created via the Ashby Integration. Existing offers created without using the Ashby integration aren't retroactively changed.

  After creating a custom field mapping, you will need to make a new update to an offer in Ashby for the mapping to take effect.
</Info>

## Add or edit a mapping

<Steps>
  <Step title="Open ClearOffer">
    Open ClearOffer and click on the `Company` toggle in the sidebar, then click on `Integrations` to open the Integrations page.
  </Step>

  <Step title="Show Custom Fields">
    Within the Ashby card, click on the `Show Custom Fields` button.
  </Step>

  <Step title="Add Mapping">
    Click `Add Mapping`, enter the exact Ashby custom field name, then choose a ClearOffer field from the dropdown.

    <Tip>
      Field names must match Ashby exactly (including spaces and casing).
    </Tip>
  </Step>

  <Step title="Edit or delete">
    Use the row actions to update or remove a mapping. Deletions require confirmation.
  </Step>
</Steps>

## Rules and recommendations

<CardGroup cols={2}>
  <Card title="Mapping rules" icon="triangle-exclamation">
    Each ClearOffer field can be mapped at most once.

    Each Ashby field name can appear at most once.
  </Card>

  <Card title="Best practices" icon="lightbulb">
    Use simple, unambiguous Ashby field titles.

    Test with a single offer before rolling out broadly.
  </Card>
</CardGroup>

## Available ClearOffer fields

<AccordionGroup>
  <Accordion title="Candidate fields">
    * Candidate First Name
    * Candidate Last Name
  </Accordion>

  <Accordion title="Core offer fields">
    * Job Title/Role
    * Department
    * Location
    * Reporting To
    * Base Salary Override
    * Currency
    * Payment Frequency
    * Welcome Message
    * Start Date
    * Expiration Date
  </Accordion>

  <Accordion title="Equity fields">
    * Equity Shares (Number)
    * Equity Type
    * Years Vesting
    * Cliff Period (Months)
    * Strike Price
    * Preferred Price
    * Outstanding Shares
    * Company Valuation
  </Accordion>

  <Accordion title="Commission fields">
    * Commission Type
    * Commission Target Amount
    * Commission Base Rate
    * Commission Quota Amount
    * Commission Payout Frequency
    * Commission Has Accelerators
    * Commission Details
  </Accordion>

  <Accordion title="Bonus fields">
    * Bonus Type
    * Bonus Name
    * Bonus Amount
    * Bonus Amount Type
    * Bonus Currency
    * Bonus Frequency
    * Bonus Description
  </Accordion>
</AccordionGroup>

## Examples

<CardGroup cols={2}>
  <Card title="Map department" icon="building">
    Ashby `Department` → ClearOffer `Department`

    Keeps your org structure consistent between systems.
  </Card>

  <Card title="Import equity details" icon="coins">
    Ashby `Equity` → ClearOffer `Equity Shares (Number)`.

    ClearOffer will create equity details using your company defaults when values aren't provided.
  </Card>
</CardGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="My mapping didn't apply">
    * Confirm the Ashby field title exactly matches what's in Ashby, and it is an `Offer` custom field
    * Ensure the offer was created/updated after the mapping was saved
    * Verify the relevant webhook event (Create/Update) is enabled in Ashby
  </Accordion>

  <Accordion title="Duplicates prevented">
    The UI blocks duplicate Ashby field names and duplicate ClearOffer fields to avoid conflicts.
  </Accordion>

  <Accordion title="Equity values not recognized">
    Ensure `Equity Shares (Number)` is a `Number` field in Ashby. Non-numeric values can't be imported.
  </Accordion>
</AccordionGroup>

## See also

<Card title="Connect Ashby" icon="plug" href="/integrations/ashby">
  Set up the Ashby integration and verify your connection.
</Card>