Using ChartHop to open jobs

in an outbound job data flow, charthop serves as the primary source of truth for open jobs depending on the status of a job in charthop, it translates to a specific status for the same job in greenhouse only one hiring manager and recruiter can be chosen in charthop and thus be synced into greenhouse as a workaround, if hiring manager and/or recruiter is blank in charthop, but multiple exist in greenhouse, syncs do not overwrite what’s in greenhouse group fields cannot be custom mapped for example a department in charthop can not be mapped to a custom greenhouse field, and a custom field in charthop can not be mapped to greenhouse department greenhouse job field values default to charthop’s if any changes are made, therefore changing an open role must be done in charthop to be accurately reflected in greenhouse however there is an exception for hiring manager and recruiter fields where the integration will not override those fields if they are left empty in charthop this is to accommodate greenhouse’s ability to have multiple hiring managers and recruiters outbound job status mappings charthop job statuses map to greenhouse job statuses in the following way charthop status data flow greenhouse opening status active → open passive → closed inactive → closed pending < offer accepted offer → does nothing remove job → opening deleted charthop jobs only change the status of greenhouse openings directly that being said, if all openings underneath a greenhouse job are deleted or closed, the greenhouse job will automatically turn to closed create a job when conducting your headcount planning in charthop, you can add new hires and new direct reports as you normally would, but with the added functionality of the outbound data flow which triggers the moment you set a specific new role(s) recruiting status to active setting a job as active triggers the outbound data flow to create a new job in charthop under an outbound job data flow, follow these steps from the left sidebar, select org chart in the org chart , create a new job by either adding a direct report by selecting add a direct report under a pre existing person or role creating a new job by selecting new hire under a pre existing person or role in the create job dialog enter your information for the new role under the following tabs structure general information about the role, including title, department, and location compensation compensation information about the role, including salary and bonuses recruiting recruiting information about the role, including hiring status and start date description a general description about the role the outbound job data flow kicks in the moment you set the recruiting status for your newly created role is set to active job hiring status any open roles with a recruiting status set to active in charthop flow from charthop to greenhouse new open jobs in charthop with an active recruiting status close in greenhouse if the job is set back to an inactive or passive status in charthop deleting a job in charthop removes the same job in greenhouse charthop job status result in greenhouse active a req is automatically created in greenhouse either as a new greenhouse job or opening, or as a new opening underneath an existing greenhouse job inactive or passive the job opening is closed in greenhouse a created charthop job set as inactive or passive does not sync over to greenhouse during the initial greenhouse job/opening creation unless it is set to active removed job the job opening is deleted in greenhouse if the job in charthop is the only opening beneath a greenhouse job, and if the opening is set to closed in greenhouse, if the charthop job is set to inactive or passive , then the job in greenhouse is automatically closed job templates when a new job is created in charthop, it copies the job posting from the matching job template configured in the greenhouse integration job template settings see docid\ vg4de4lcfokcssaqz9ier for more infor job matching with match jobs by job code enabled in the greenhouse integration settings, all charthop jobs match with their respective greenhouse jobs according to the greenhouse job’s requisition id new jobs created in charthop with a job code are reflected in greenhouse with the job code's name (settings > groups > job codes) instead of the job's title if match jobs by job code is disabled, no job codes exist, or if no match is found via job codes, the initial mappings are then determined by your group job openings settings (for example title , title and location , or none ) for example, if title is selected, then a charthop job is created as a greenhouse opening underneath a greenhouse job that has the same title once the initial mappings are set, the job in charthop is tied to the job in greenhouse through the greenhouse job id ( greenhouseid) field in charthop charthop stores both the job id and opening id in the greenhouse job id ( greenhouseid ) field, separated by a slash for example, if greenhouseid has a value of 123/456, that means the job id has a value of 123 and the opening id has a value of 456 creating a job generates the greenhouseid denoted as jobid/openingid the opening id is not the opening id field in the greenhouse ui it is the api assigned opening id if no “req code” is provided in charthop, charthop automatically sets the opening id in the greenhouse ui to the api assigned opening id however, changing the opening id in the greenhouse ui will not change the api assigned opening id, so manually changing the greenhouseid in charthop is not recommended job matching when merging roles to primary in a scenario when managing an outbound data flow in a charthop scenario, you should be aware of the logic used in order to match the jobs once you create a new job in charthop or update the job to active through the org chart, or using a merged scenario, the new job information migrates to greenhouse if a job match can't be found in greenhouse, a new greenhouse job is created via the job’s template the job post tied to the newly created greenhouse job is the job post specified according to the job’s assigned job template in the greenhouse integration app’s settings as a recruiter, after an initial sync, you can navigate to greenhouse and update all of the pertinent information pertaining to a role that is not updated in charthop, such as the job’s description with this done, you can begin actively recruiting for the open role reconcile data during a sync, you may run into inconsistencies with your data due to sync failures or changes in the custom field mappings to handle these cases, you can enable the greenhouse integration app's reconciliation feature with run daily enabled in the greenhouse integration app configuration settings, reconciliations are triggered on a daily basis you may also manually trigger the reconciliation by selecting the sync greenhouse jobs button located at the base of the greenhouse integration app settings page reconciliations are only available for outbound job data flows select the run a one time sync button to manually trigger a reconciliation to manually run a data sync reconciliation from the left sidebar, select apps & bundles from the sub menu, select apps select the installed apps tab scroll the list down to the greenhouse app select the greenhouse app from the charthop greenhouse app settings page, scroll down to the bottom of the settings page select sync greenhouse jobs