Update API key creation instructions in greenhouse.mdx

baton/greenhouse.mdx

@@ -2,7 +2,7 @@
 title: "Set up a Greenhouse connector"
 og:title: "Set up a Greenhouse connector"
 description: "C1 provides identity governance and just-in-time provisioning for Greenhouse. Integrate your Greenhouse instance with C1 to run user access reviews (UARs) and enable just-in-time access requests."
 og:description: "C1 provides identity governance and just-in-time provisioning for Greenhouse. Integrate your Greenhouse instance with C1 to run user access reviews (UARs) and enable just-in-time access requests."
 sidebarTitle: "Greenhouse"
 ---
 
@@ -15,7 +15,7 @@
 
 The Greenhouse connector supports [automatic account provisioning](/product/admin/account-provisioning). Note that newly provisioned accounts will be created with Basic user permissions. 
 
 This connector does not support account deprovisioning. You must deprovision accounts directly in Greenhouse.
 
 The connector syncs roles, including roles for job permissions and future job permissions. 
 
@@ -41,10 +41,18 @@
 <Step>
 Click **Create new API key** and fill out the form:
 
-   - **API Type**: Harvest
-   - **Partner**: Custom integration
-   - **Description**: C1 integration
+  * **API Type**: **Harvest** (not *Harvest v3 (OAuth)* — see the note below)
+  * **Partner**: Custom integration
+  * **Description**: C1 integration
 </Step>
+<Note>
+
+  **Harvest vs. Harvest v3 (OAuth).** Greenhouse offers two Harvest credential types. The C1 connector uses the legacy **Harvest** key, which Greenhouse treats as a username with no password. The connector has a single **Greenhouse username (API token)** field and no secret field for this reason.
+
+A **Harvest v3 (OAuth)** credential produces a Client ID and Client Secret. These will not work with the connector
+
+
+</Note>
 <Step>
 Click **Manage Permissions**. The new key is generated.
 </Step>
@@ -98,7 +106,7 @@
 <Step>
 Choose how to set up the new Greenhouse connector:
 
    - Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
 
    - Add the connector to a managed app (select from the list of existing managed apps)
 
@@ -119,7 +127,7 @@
 Paste your Greenhouse API token into the **Greenhouse Username (API Token)** field. (Greenhouse uses API tokens as usernames when authenticating.)
 </Step>
 <Step>
 **Optional.** If you're using the Greenhouse connector to deprovision Site Admin user permissions, enter the email of a user with Site Admin permissions in the **On behalf of** field. This email address will be logged as the [responsible party for the permission change in the Greenhouse audit log](https://developers.greenhouse.io/harvest.html#delete-remove-a-job-permission).
 </Step>
 <Step>
 Click **Save**.
@@ -153,7 +161,7 @@
 <Step>
 Choose how to set up the new Greenhouse connector:
 
    - Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
 
    - Add the connector to a managed app (select from the list of existing managed apps)
 
@@ -244,7 +252,7 @@
 
 <Steps>
 <Step>
 Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
 </Step>
 <Step>
 Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Greenhouse connector to. Greenhouse data should be found on the **Entitlements** and **Accounts** tabs.