Troubleshooting the Lever integration

This section covers a series of potential issues you may run into when setting up or configuring your Lever Requisitions App in ChartHop, as well as their recommended solutions.

In case a jobs fails to be properly created, you can check for the following:

1. Confirm that your API and Webhook credentials are correct.
2. Confirm that your Hiring Manager and Recruiter have accounts in both ChartHop and Lever with the same email address.
3. Ensure that your teams match between ChartHop and Lever.

4. Ensure that there are no teams with the same name across different departments in Lever. Please contact support@charthop.com should this occur.

In the case a hiring fails, you can check the following:

1. Confirm that an email has been provided for the candidate
2. Ensure that the Lever Req ID field is mapped to the correct job. You can contact support@charthop.com if you need assistance with this.
3. Be aware that we do not support internal transfers.

There are two access levels in ChartHop specifically designed for Recruiters: 

1. Recruiting Editor: These users are allowed to view and make changes to open jobs, including target compensation levels and sensitive jobs. They are not allowed to make changes to, or access sensitive data about current employees, other than those they manage. This permission is generally intended for Recruiting roles or those managing the ATS.
2. Recruiting View: These users are allowed to view sensitive information about open jobs only, including target compensation levels and viewing all sensitive jobs. They are not allowed to make changes to the primary timeline, or access sensitive information about current employees other than those they manage.

Other access levels with the ability to open roles: 

Primary Editor: These users are allowed to view all information, and make official, permanent changes to the primary timeline. This access should be restricted tightly and limited to a few authorized individuals in HR, Finance, or similar roles.

Owner: These users are allowed full access to everything, including the ability to change user permissions, configure integrations, and alter organization-wide settings. Because of the scope involved, this access should be tightly restricted.