For the complete documentation index, see llms.txt
For the complete documentation index, see llms.txt
Zinc
Help center
How to Change the Email Address Used for Background Checks in Your ATS
### Who will the background check email come from
When you initiate a background check, the email request will always be sent from the email address associated with the API Key holder in your Zinc account. This is typically the person who initially set up the integration and generated the API Key or the main user in Zinc.
### What happens if that user is removed
If the user is removed from the system, the API Key automatically transfers to the person who removed them from your Zinc Account. This new user will inherit the credentials and become the main user or API Key Holder. From that point on, all background check emails will be sent from their email address.
### Can requests come from different emails
Nope! Background check requests will always be sent from the API Key holder’s email, no matter who kicks off the request from the ATS.
### How to change the sending email
If you need background check emails to come from a different email address, you’ll need to transfer API Key ownership to a new user.
1. **Remove the current API Key holder** – An admin should remove the current API Key holder from the Zinc account.
2. **New user inherits the API Key** – The person who removed the old user will automatically become the new API Key holder.
3. **Confirm the new sending email** – Once the transition is done, all background check emails will now be sent from the new user email.
4. **(Optional) Re-add the previous API Key holder** – If you don’t want to permanently remove the previous key holder, you can add them back to the Zinc account after the transfer. They can have the same user role as before, but they will no longer be the API Key holder.
### Can I just change the API key instead of removing the user?
No—if your goal is to change the email address the background-check request emails come from, you need to transfer API Key ownership, which is done by removing the current API Key holder (and then re-adding them afterward if needed).