From 32d3d606ce80bcca7bdd21f1334070ad0ae21339 Mon Sep 17 00:00:00 2001 From: Jeran Norman Date: Tue, 11 Aug 2026 18:47:16 +0300 Subject: [PATCH 1/4] docs(greenhouse): rewrite IAM guide for Harvest V3 OAuth credentials and reconnection Greenhouse is retiring Harvest v1/v2 API keys, so the connection guide now walks through creating Harvest V3 OAuth credentials (Client ID/Secret), configuring scopes, and reconnecting an existing account instead of recreating it. Drops screenshots that show the old single-API-key flow (image2, image3, image6, image7); keeps the two that are still accurate (image1 nav path, the user-ID-in-URL screenshot). New Dev Center and Hub-reconnect screenshots are a follow-up capture, not included here. --- connection-guides/iam/greenhouse.mdx | 95 ++++++++++++++++------------ 1 file changed, 54 insertions(+), 41 deletions(-) diff --git a/connection-guides/iam/greenhouse.mdx b/connection-guides/iam/greenhouse.mdx index 6214c97..8b7bd8d 100644 --- a/connection-guides/iam/greenhouse.mdx +++ b/connection-guides/iam/greenhouse.mdx @@ -8,68 +8,81 @@ description: "If you have been directed to StackOne to integrate with Greenhouse This guidance assumes you have Admin privileges for your Greenhouse account. +Greenhouse is retiring the Harvest v1 and v2 API keys. The StackOne integration now connects using Harvest V3 OAuth credentials, a Client ID and Client Secret you generate in the Greenhouse Dev Center, instead of a single API key. -## Generating Harvest API Key +If you already have a Greenhouse account connected to StackOne, you don't need to disconnect and set up a new one. Reconnect that same account with your new Harvest V3 credentials. Your account ID and everything you've already configured stay exactly as they are, and your existing syncs keep running once you've reconnected. - - - Click on Configure gear ⚙️ and open Dev Center > API credentials. - ​ - - ![Step 1](/images/greenhouse/image1.png) - - - - Click Create new API key. Specify the following parameters: +## Create Harvest V3 OAuth credentials - API type – Harvest + + Creating credentials requires admin access with the "Can manage ALL organization's API Credentials" permission in Greenhouse. + - Partner – Custom + + + Click the Configure gear in the top navigation, then Dev Center on the left, then API Credentials. - Description – "Describe_your_integration" - ​ - ![Step 2](/images/greenhouse/image2.png) + Open API Credentials in Greenhouse Dev Center - - Click Manage permissions. - - Copy your newly generated API key to a safe place. Then click **I have stored the API key**. - - ![Step 3](/images/greenhouse/image3.png) - + + Click Create new API credentials. Set the API type to **Harvest V3 (OAuth)** and enter a description, for example "StackOne Integration". - - In the Manage permissions page, enable Select the following 2 permissions and click **Save**: - - User Roles - - Users - ​ - - ![Step 4](/images/greenhouse/image6.png) - + + Greenhouse shows the Client Secret only once. Copy both the Client ID and the Client Secret and store them somewhere safe before you close the dialog. If you lose the secret, you'll need to create a new credential. -## Retrieve your Greenhouse User ID -Per the Greenhouse documentation, you can locate a User ID by going to the **Users** page, select a User with the **Site Admin** permission and retrieve the User ID present in the URL: +## Configure scopes + +Open the Settings tab on your new credential and go to Manage Scopes. Select the Harvest dropdown and enable at least the `harvest:users:list` scope. StackOne needs it to list your Greenhouse users. + +## Find your User ID (optional) -*Screenshot of an example User ID:* +StackOne can act on behalf of a specific Greenhouse user when it calls the API. To set this up, open that user in Greenhouse and copy the numeric ID from the URL. For example, `https://app.greenhouse.io/account/users/12345678/edit` gives you the ID `12345678`. -![Step 6](/images/greenhouse/10577285508763.png) + Greenhouse user ID shown in the profile URL +The user you choose needs Site Admin permissions. Greenhouse only lets Site Admins list users, so a User ID that isn't a Site Admin will cause user listing to fail. + +If you leave this field blank, StackOne acts as the auto-generated service account attached to your credentials instead of a specific user. + ## Connect with StackOne -Enter the gathered details in the relevant inputs and proceed by clicking the Connect button. - -![Step 7](/images/greenhouse/image7.png) - +If this is your first time connecting Greenhouse to StackOne, open the Link Account form and enter: + +
    +
  • Client ID
    • +
  • Client Secret
    • +
  • User ID (optional)
    • +
+ +Then click Connect. + +## Reconnect your existing account + +If you already have a Greenhouse account connected, reconnect it instead of creating a new one. + + + Go to Accounts in the StackOne Hub and find your existing Greenhouse account. + + + + Select Reconnect on that account (this may be labeled Edit connection). + + + + Enter the Client ID and Client Secret you copied earlier, plus the User ID if you're using one, then save. + + +Reconnecting keeps the same account ID and every setting you already had configured. Your syncs keep running once the new credentials are saved, there's nothing else to redo. ## Available data @@ -81,6 +94,6 @@ This integration has the following [IAM Resources](https://docs.stackone.com/ref ## Useful Links - - https://developers.greenhouse.io/harvest.html + + https://harvestdocs.greenhouse.io/docs/authentication From f32576bac6c569954dd8ca222a46998e6b5f922e Mon Sep 17 00:00:00 2001 From: Jeran Norman Date: Wed, 12 Aug 2026 23:18:23 +0300 Subject: [PATCH 2/4] docs(greenhouse): match portal labels and repo formatting conventions Renames the Dev Center menu item to API Credential Management, adds the Configure > Users path and Export to Excel tip for finding a User ID, adds the harvest:user_roles:list scope needed for the Roles resource, folds the scope step into the Steps block, and bolds UI labels in line with the other connection guides. --- connection-guides/iam/greenhouse.mdx | 52 +++++++++++++--------------- 1 file changed, 25 insertions(+), 27 deletions(-) diff --git a/connection-guides/iam/greenhouse.mdx b/connection-guides/iam/greenhouse.mdx index 8b7bd8d..3588987 100644 --- a/connection-guides/iam/greenhouse.mdx +++ b/connection-guides/iam/greenhouse.mdx @@ -5,7 +5,7 @@ description: "If you have been directed to StackOne to integrate with Greenhouse - This guidance assumes you have Admin privileges for your Greenhouse account. + This guidance assumes you have Admin privileges for your Greenhouse account, including the "Can manage ALL organization's API Credentials" permission. Greenhouse is retiring the Harvest v1 and v2 API keys. The StackOne integration now connects using Harvest V3 OAuth credentials, a Client ID and Client Secret you generate in the Greenhouse Dev Center, instead of a single API key. @@ -14,75 +14,73 @@ If you already have a Greenhouse account connected to StackOne, you don't need t ## Create Harvest V3 OAuth credentials - - Creating credentials requires admin access with the "Can manage ALL organization's API Credentials" permission in Greenhouse. - - - - Click the Configure gear in the top navigation, then Dev Center on the left, then API Credentials. + + Click the **Configure** icon on the navigation bar, click **Dev Center** on the left menu, then click **API Credential Management**. - Open API Credentials in Greenhouse Dev Center + Open API Credential Management in the Greenhouse Dev Center - Click Create new API credentials. Set the API type to **Harvest V3 (OAuth)** and enter a description, for example "StackOne Integration". + Click **Create new API credentials**, select **Harvest V3 (OAuth)** as the API type, and enter a description, for example "StackOne Integration". - Greenhouse shows the Client Secret only once. Copy both the Client ID and the Client Secret and store them somewhere safe before you close the dialog. If you lose the secret, you'll need to create a new credential. + Copy both the **Client ID** and the **Client Secret** and store them somewhere safe before you close the dialog. Greenhouse shows the Client Secret only once. If you lose it, you'll need to create a new credential. - -## Configure scopes - -Open the Settings tab on your new credential and go to Manage Scopes. Select the Harvest dropdown and enable at least the `harvest:users:list` scope. StackOne needs it to list your Greenhouse users. + + Open the **Settings** tab of your new credentials. Under **Manage Scopes**, click the **Harvest** dropdown and enable the scopes StackOne needs to read your users and their roles: + - `harvest:users:list` + - `harvest:user_roles:list` + + ## Find your User ID (optional) -StackOne can act on behalf of a specific Greenhouse user when it calls the API. To set this up, open that user in Greenhouse and copy the numeric ID from the URL. For example, `https://app.greenhouse.io/account/users/12345678/edit` gives you the ID `12345678`. +StackOne can act on behalf of a specific Greenhouse user when it calls the API. To set this up, go to **Configure > Users**, click the user, and copy the numeric ID from the browser URL. For example, `https://app.greenhouse.io/account/users/12345678/edit` gives you the ID `12345678`. Greenhouse user ID shown in the profile URL +To find your own User ID, locate your account in the list (marked **"(you)"**), click **Export to Excel**, and read your ID from the **User ID** column. + The user you choose needs Site Admin permissions. Greenhouse only lets Site Admins list users, so a User ID that isn't a Site Admin will cause user listing to fail. If you leave this field blank, StackOne acts as the auto-generated service account attached to your credentials instead of a specific user. ## Connect with StackOne -If this is your first time connecting Greenhouse to StackOne, open the Link Account form and enter: +If this is your first time connecting Greenhouse to StackOne, go to **Accounts > Link Account > Greenhouse** and enter: - +- **Client ID** +- **Client Secret** +- **User ID** (optional) -Then click Connect. +Then click **Connect**. ## Reconnect your existing account If you already have a Greenhouse account connected, reconnect it instead of creating a new one. - - Go to Accounts in the StackOne Hub and find your existing Greenhouse account. + + Go to **Accounts** in the StackOne Hub and find your existing Greenhouse account. - Select Reconnect on that account (this may be labeled Edit connection). + Select **Reconnect** on that account. This may be labelled **Edit connection**. - Enter the Client ID and Client Secret you copied earlier, plus the User ID if you're using one, then save. + Enter the **Client ID** and **Client Secret** you copied earlier, plus the **User ID** if you're using one, then save. -Reconnecting keeps the same account ID and every setting you already had configured. Your syncs keep running once the new credentials are saved, there's nothing else to redo. +Reconnecting keeps the same account ID and every setting you already had configured. Your syncs keep running once the new credentials are saved, so there is nothing else to redo. ## Available data From f95e54d94c3afca2629695323154f06a954ebb73 Mon Sep 17 00:00:00 2001 From: Jeran Norman Date: Wed, 12 Aug 2026 23:30:39 +0300 Subject: [PATCH 3/4] docs(greenhouse): add retirement date, correct nav icon, drop reconnection section Adds the August 31, 2026 retirement date for Harvest v1 and v2 keys, renames the navigation icon to Settings, and removes the reconnection guidance in favour of one connect section that covers both cases. --- connection-guides/iam/greenhouse.mdx | 28 +++------------------------- 1 file changed, 3 insertions(+), 25 deletions(-) diff --git a/connection-guides/iam/greenhouse.mdx b/connection-guides/iam/greenhouse.mdx index 3588987..0bacd0c 100644 --- a/connection-guides/iam/greenhouse.mdx +++ b/connection-guides/iam/greenhouse.mdx @@ -8,15 +8,13 @@ description: "If you have been directed to StackOne to integrate with Greenhouse This guidance assumes you have Admin privileges for your Greenhouse account, including the "Can manage ALL organization's API Credentials" permission. -Greenhouse is retiring the Harvest v1 and v2 API keys. The StackOne integration now connects using Harvest V3 OAuth credentials, a Client ID and Client Secret you generate in the Greenhouse Dev Center, instead of a single API key. - -If you already have a Greenhouse account connected to StackOne, you don't need to disconnect and set up a new one. Reconnect that same account with your new Harvest V3 credentials. Your account ID and everything you've already configured stay exactly as they are, and your existing syncs keep running once you've reconnected. +Greenhouse is retiring the Harvest v1 and v2 API keys on August 31, 2026. The StackOne integration now connects using Harvest V3 OAuth credentials, a Client ID and Client Secret you generate in the Greenhouse Dev Center, instead of a single API key. ## Create Harvest V3 OAuth credentials - Click the **Configure** icon on the navigation bar, click **Dev Center** on the left menu, then click **API Credential Management**. + Click the **Settings** icon on the navigation bar, click **Dev Center** on the left menu, then click **API Credential Management**. Open API Credential Management in the Greenhouse Dev Center @@ -54,7 +52,7 @@ If you leave this field blank, StackOne acts as the auto-generated service accou ## Connect with StackOne -If this is your first time connecting Greenhouse to StackOne, go to **Accounts > Link Account > Greenhouse** and enter: +To connect or reconnect your Greenhouse account, enter: - **Client ID** - **Client Secret** @@ -62,26 +60,6 @@ If this is your first time connecting Greenhouse to StackOne, go to **Accounts > Then click **Connect**. -## Reconnect your existing account - -If you already have a Greenhouse account connected, reconnect it instead of creating a new one. - - - - Go to **Accounts** in the StackOne Hub and find your existing Greenhouse account. - - - - Select **Reconnect** on that account. This may be labelled **Edit connection**. - - - - Enter the **Client ID** and **Client Secret** you copied earlier, plus the **User ID** if you're using one, then save. - - - -Reconnecting keeps the same account ID and every setting you already had configured. Your syncs keep running once the new credentials are saved, so there is nothing else to redo. - ## Available data This integration has the following [IAM Resources](https://docs.stackone.com/reference/iam_list_users) available from the provider: From 93ec2d02255e90b1dbbb5ccdb4776d72ef95bb56 Mon Sep 17 00:00:00 2001 From: Jeran Norman Date: Wed, 12 Aug 2026 23:39:15 +0300 Subject: [PATCH 4/4] docs(greenhouse): restore Configure as the navigation icon name --- connection-guides/iam/greenhouse.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/connection-guides/iam/greenhouse.mdx b/connection-guides/iam/greenhouse.mdx index 0bacd0c..f974af1 100644 --- a/connection-guides/iam/greenhouse.mdx +++ b/connection-guides/iam/greenhouse.mdx @@ -14,7 +14,7 @@ Greenhouse is retiring the Harvest v1 and v2 API keys on August 31, 2026. The St - Click the **Settings** icon on the navigation bar, click **Dev Center** on the left menu, then click **API Credential Management**. + Click the **Configure** icon on the navigation bar, click **Dev Center** on the left menu, then click **API Credential Management**. Open API Credential Management in the Greenhouse Dev Center