Using ChartHop to open jobs

p ackages basic basic | | standard standard | premium available as an add on when you configure your lever acquisitions app to have an outbound 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 lever open job creation recommendations when you use charthop to open jobs in an outbound data sync, there are a few things to note syncing outbound from charthop to lever bypasses approval workflows in lever as a result, you should leverage scenarios in charthop when proposing new open roles or edits to open roles lever requisition field values are updated to charthop’s if any changes are made, therefore you should only make changes in charthop to mapped fields as opposed to directly in lever only one location is accepted in lever, so if multiple locations are present in charthop, only the first location will be passed into lever a d epartm ent in charthop cannot be mapped to a custom lever field, and a custom field in charthop cannot be mapped to lever department outbound job status mappings charthop job statuses map to lever job statuses in the following ways 268,92,383 false true unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type create a job with the lever requisitions app enabled, charthop's open jobs list becomes the system of record for open jobs recruiters, hiring managers, financial planners, and team leads can all look at charthop for a real time view of which roles are open and how recruiting is going without needing access to lever to avoid potential org data issues, we recom mende d that you create new jobs via scenarios as opposed to directly in primary when an open job in charthop is set to active recruiting status (either when someone creates or updates a new job), a req code is automatically created in lever if not provided in charthop manually the mapped lever requisition is changed to on hold in lever if the open job is set back to an inactive status similarly, when the job is removed from charthop, it is deleted in lever if you create a new job in charthop with a recruiting status set to active without a req code, a new req code is automatically generated by looking through the most recent req codes for that department, and incrementing the number (for example, from eng 8 to eng 9) setting a job as active in charthop opens a new job in lever to create a new job in charthop, 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 using your custom fields and charthop’s recommended fields beneath 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 once a candidate is hired in lever, the job in charthop is set to pending status , and the hired candidate is an nounced in charthop, with their start date being the specified start date in the lever offer job hiring status any open roles with a recruiting status set to active in charthop flow from charthop to lever mapped lever requisitions are placed on hold in lever if the mapped charthop job is changed to an inactive or passive status in charthop the mapped lever requisition is deleted if the charthop job is removed 121,622 trueleft unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type reconcile data you can fix any data discrepancies by forcing charthop to reconcile data with lever outside of a regularly scheduled sync to handle these cases in bulk, you can enable the lever requisitions integration app's reconciliation feature during a data reconciliation, charthop bulk changes all lever requisitions to match what is in charthop with run daily enabled in the lever requisitions integration app configuration settings, reconciliations are triggered on a daily basis you may also manually trigger the reconciliation by selecting the sync jobs button located at the base of the app settings page select the run a one time sync button to manually trigger a reconciliation reconciliations are only available for outbound job data flows 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 lever requisitions app select the lever requisitions app from the charthop lever requisitions app settings page, scroll down to the bottom of the settings page select sync jobs