Jobvite Staging (Testing) Environment

Staging is a environment that we use to test. We also allow users to access staging to help us in beta testing new functionality or conduct other related testing. 

Here is the link to the current staging environment, so you can further test the new features we are releasing at Jobvite:

A few things to keep in mind with the staging environment:

1. No e-mails are sent from Staging, but communications are included on the Messages tab. This is by design so you can test away without worrying about spamming anyone.  If there is a compelling purpose for sending emails from the staging environment, though, we can temporarily enable this for you.  Please contact our Support Team for assistance.  

2. The staging environment refreshes with new data taken from your production environment data on approximately 6-week intervals.  The refresh will typically occur during the weekend, beginning on Friday evening PST and completing by Sunday afternoon PST.  There are exceptions from time to time to postpone the refresh, but they are very rare and do not affect the functionality of staging. 

Important Note: While the refresh process begins on Friday evening in the staging environment, the copying of your production data occurs some time on Thursday, preceding the Friday refresh.  Therefore, if you want any settings or other data to populate in your staging environment, you should enter that data in your production environment as of the end of the day on Wednesday, prior to the staging refresh. 

Scheduling Note: When in the staging environment, you can always check the Next Refresh Date button at the top of the Dashboard page.


During a staging refresh, current company data is copied from production into staging, so any changes that have been made only in staging will be overwritten. If you are planning on longer term testing in staging it is recommended to build as much as possible in production first (and leave it inactive there) so that in the event of a staging refresh as much as possible is transferred from production.​

3. There is no Service Level Agreement for Staging like there is for Production and it may be unavailable at any time without notice, (but is also provided to you at no additional monthly charge).

4. Any changes made in Staging [only] will be lost every time there is a database refresh, which essentially resets everything to the way your current production environment is set up.

5. There are automated deployments using Staging every day as our engineers work on the platform. On or near these times, the site might be down or you could experience odd behavior.  Even if you do notice a slowdown, you should find that the behavior returns to normal within 10-15 minutes.

6. It is important to remember that our Staging environment is not a Sandbox environment that mirrors your Production environment; essentially, they are separate databases, with your production environment supplying the raw material for your staging environment, renewed/updated approximately 1 time per month.  With this in mind, no work you do in your staging environment will carry over to your production environment - this is simply not the way the 2 systems are set up.


Note: This is a new(er) staging environment URL.  If you have bookmarked or saved any reference to, please remove those from your browsers; that staging environment was deprecated as of late 2019.  This also applies to API interactions with staging; all calls need to use in place of the former endpoint.

Our new environment has improved performance, capacity, and security/redundancy.

If you have any issues accessing the staging environment, you may need to review the following transitional steps:

What do I need to do as Jobvite admin?  

  1. Use the URL to access your Jobvite staging site (and for api calls)
  2. Notify your technical team about the recent change in staging environment URLs

What does my technical team need to do?

  1. Allow and ensure access to from corporate environment 
  2. Contact your company’s IT and Security teams and request the permit access to these IP’s through the firewall: a. b.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful