To assist users in compliance with various consumer privacy and data security laws, rules, and regulations around the world, Bullhorn provides the Consent Management tool to track candidate consent data. Matador Jobs Pro will collect data on user consents from Matador Jobs forms and, when processing applications into Bullhorn, will sync that consent data into the Bullhorn Consent Management tool.
Why Manage Candidate Consents?
In 2018, with the pending implementation of the European Union’s General Data Privacy Regulation, all web site operators were put on notice that responsible handling and use of user data was now an obligation. Since then, hundreds of jurisdictions have implemented similar laws, meaning almost anywhere you’re running your business, you will need to manage your user data.
A key aspect of managing user data is how you use it, including what you can and cannot do with it and for what actions you must have explicit user consent. Data privacy laws generally require you to keep track of when and to what extent each user granted you permission to use their data, including whether you can evaluate their data (such as in determining fitness for the position for which they applied) and whether you can share their data with 3rd parties (such as submitting their data to a client hiring manager for interviews and on-boarding).
Of course, while one would assume that when a user visits your website and applies for a job, they implicitly agree to allow you to use that data; however, it is wise for you to keep specific track of when and how they provided that consent.
Matador Jobs Pro will collect candidate’s consent data from all submissions and sync that data to Bullhorn’s Consent Management tool. We do this important, and increasingly compulsory, task for you seamlessly and without complex setup or configuration.
How Matador Tracks & Syncs Candidate Consents
When a user applies for a position on a Matador Jobs Pro powered website, Matador saves information they provided during their interaction. Notably, if you have the “Require Applicant to Agree to Privacy Policy” setting turned on, which nearly all our users do, this is the default consent Matador tracks.
During application processing, Matador Jobs will create Bullhorn Consent Management records for each collected consent. Upon sync with Bullhorn, these records will be saved onto the Candidate’s record.
The best part is that all of this happens automatically provided the following is in place:
- Your Bullhorn ATS account has the Consent Management tool enabled
- Your Bullhorn API Credentials for Matador has permissions enabled to access and update the data on the Consent Management tool.
Finally, it is worth noting that if your site has the “Delete Local Applications After Sync” setting turned on, which is recommended as a best practice, once the application is synced, the consent data will exist only on Bullhorn. For this reason, it is critical you ensure Consent Management is accessible by your Matador Jobs Pro powered site.
What Happens When Matador Can’t Save Consents?
If either of the two conditions stated above are not in place, Matador Jobs Pro cannot save candidate consent data to the Bullhorn Consent Management tool. How Matador Jobs Pro behaves varies drastically depending on which one of the conditions fails.
What Happens When Matador Can’t Find the Consent Management Tool Enabled?
When Matador Jobs Pro cannot detect the Consent Management tool installed on your ATS, Matador Jobs Pro does… nothing. Some users do not want to track candidate consent, either because they do not feel they are currently subject to laws requiring it or because they have other methods in place to track this data. For this reason, Matador assumes the lack of the Consent Management tool means the user does not want Matador tracking this data.
There is no error message, admin notification, log message, or email produced by Matador when it fails to find a Consent Management object in your API.This is to ensure that Matador does not behave in an annoying way to users who choose to not use Consent Management (for example, if you use another tool to track consent.)
If Matador does not find the Consent Management Tool, Matador will discard candidate consent data along with the application data upon successful sync.
What Happens When Matador Lacks Permissions to Access the Consent Management Tool?
That said, if Matador can detect the Consent Management tool installed on your ATS, Matador Jobs will automatically try to save candidate consents data. Sometimes, however, it will be unable to because the logged in user lacks permission to modify the Consent Management tool data.
We will be aware of this because, upon submission, a candidate’s create or update call to the API will generate an error back from the Bullhorn API with the text errors.entitlements.customObjectFieldPermission. If we encounter this, we know the logged in user is unable to edit the Consent Management object.
In this case, contrary to what happens when the Consent Management tool is not detected, Matador will be annoying! Every 24 hours, Matador will email the administrator notifying them of the issue. There will be log items repeated over and over in your logs, and we will be adding even more notifications in the future. We do this because we believe if the Consent Management object is found, you want Matador to save candidate consents data.
That said, when Matador lacks the permissions to write to the Consent Management tool, this completely interrupts the processing of candidate applications. Since it could take days for an Administrator to fix this issue, this can be very disruptive for your company. When Matador Jobs Pro encounters a permissions error, it puts a 24-hour hold on processing candidate consents data. During the 24 hours, Matador will allow applications to process without candidate consents data so the rest of the important data will sync in a timely manner. At the end of the 24-hour period, Matador will retry accessing the Consent Management tool, resulting in either another 24-hour hold or a resumption of processing candidate consents data.
Enabling/Fixing User Consent Access
If your site is not saving user consent data and/or it is reporting issues with managing user consent data, you may need to do some troubleshooting. When there is a problem, it is likely that Matador Jobs has encountered one of two issues when attempting to save user consent data to Bullhorn. They are:
- The Bullhorn Consent Management does not exist on your account.
- Matador is connected to Bullhorn via the “cookie bug” with a user who lacks permission to modify the Candidate Consent object.
- Matador is connected to Bullhorn with an API “user” that lacks the permissions to interact with the Candidate Consent object.
Have the Consent Management Tool Added to Your ATS
If you don’t have the Consent Management tool on your account, a quick Bullhorn Support ticket can get it added. If you’d like, copy and paste this support ticket draft and fill in the appropriate blanks:
Dear Bullhorn Support,
We use Matador Jobs Pro to accept applications from candidates on our website. Matador Jobs Pro collects data on user consent that we’d like to have saved to the Consent Management custom object, but we believe it is not yet enabled on our account. Will you please update our account so that we can take advantage of the Candidate Consent Management tab?
Also, please ensure our API User for Matador Jobs can always access the consent management custom object on the candidate entity. Thank you! Here is some information on our setup to help you know which API user to grant this permission to:
API Client ID: [FILL IN FROM WEBSITE OR EMAIL]
API User ID: [FILL IN FROM WEBSITE OR EMAIL]
Thank you!
[YOUR NAME]
Double Check for the “Cookie Bug”
If you begin to receive permissions errors that you weren’t seeing previously, double check that you or someone on your team has not inadvertently enabled the “cookie bug.” If after doing a “Reset Connection Assistant” routine, Matador has Consent Object permissions, you were likely affected by the “Cookie Bug.”
Requesting Consent Management Permissions Update
If you’ve verified the permissions error is not caused by the “cookie bug”, the only way to fix the permissions error is to request help of Bullhorn support. Submit a ticket and ask them to grant the Matador Jobs designated API user full access to the Consent Management “custom object.” To simplify the process, you can copy and paste the text below. Be sure to fill in the blanks with data from your installation:
Dear Bullhorn Support,
We use Matador Jobs Pro to accept applications from candidates on our website. Matador Jobs Pro collects data on user consent that we’d like to have saved to the Consent Management custom object, but Matador Jobs Pro is notifying us that it lacks permission to do so.
Will you please update our API User to be able to always access the consent management custom object on the candidate entity? Thank you! Here is some information on our setup to help you know which API user to grant this permission to:
API Client ID: [FILL IN FROM WEBSITE OR EMAIL]
API User ID: [FILL IN FROM WEBSITE OR EMAIL]
Consent Object ID:[FILL IN FROM WEBSITE OR EMAIL, IF ABLE]
Thank you!
[YOUR NAME]
Resetting the 24-Hour “Break”
As stated above, when Matador Jobs encounters a permissions error, it enables a 24-hour “break” from attempting to sync candidate consents.
If you know you have made a change that could fix the permissions and don’t want to wait to test it, you will need to delete the transient.
- Go to Plugins > Add New
- Search for “Transients Manager” by Pippin Williamson and/or Awesome Motive. Install it on your WordPress site and activate it.
- Go to Tools > Transients (you may need to refresh your WordPress admin)
- Find the transient named
bullhorn_consent_object_skipand delete it.
That’s it! On the next candidate submission, Matador will try to (and hopefully succeed) at saving candidate consents data to the Consent Management tool at Bullhorn!