Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

    English (US)
    MX Spanish (Mexico)
    CA French (Canada)
    US English (US)
    • Home
    • Getting Started

    Paradox instance policy

    Written by Lindsey Stanifer

    Updated at September 18th, 2026

    Contact Us

    If you still have questions or prefer to get help directly from an agent, please submit a request.
    We’ll get back to you as soon as possible.

    Please fill out the contact form below and we will reply as soon as possible.

    • Getting Started
      Setting up your calendar Managing your alerts Additional Settings
    • Daily Processes
      Candidate Inbox Candidate Profile My Calendar/Calendars Browser Extension My Jobs Approvals Engine Manual and Common Scheduling Practices Form I-9 processes Forms & Offers Recruiting Dashboard
    • Candidate and User Engagement
      Campaigns Conversation Builder Surveys Channels/Phone Numbers Talent Community Voice Web Management Analytics & Reporting Data Privacy Career Sites Multilingual Source Tracking
    • Management Tools
      Job Management Scheduling Security Journeys Content Management System (CMS) Multiple Brands Workflows Users, Roles and Permissions Data Feeds Location Management Lookup Tables Assistant Messaging Company Information Client Setup System Attributes Integration Center Workday Implementation
    • Contextual AI
      Knowledge Training Library
    • Conversational Events and Campus
      Conversational Events Campus Events
    • Employee Communications
      Communications App Employee Management
    • Release Notes
      2026 2025
    • Workday Feature Descriptions
    + More

    Table of Contents

    Non-Franchise Initial Paradox Deployment Franchise Deployment Entitlements: Initial Set up Paradox Instance Types Paradox Extend and Optimize Instance Purchase or Renewal

    This document defines the Workday Paradox instance policy for all eligible customers. This policy is effective January 1, 2026. Each instance has a unique URL and will always be on the same version of Paradox.


    Non-Franchise Initial Paradox Deployment

    • Candidate Experience: 2 instances (staging and production) and 1 Demo instance. 
    • Conversational ATS: 2 instances (staging and production)  and 1 Demo instance.
    • Candidate Engagement: 2 instances (staging and production)  and 1 Demo instance.

    Franchise Deployment Entitlements: Initial Set up

    Initial deployment of one or more Paradox products: Candidate Experience, Conversational ATS, Candidate Engagement:

    • Deployment large (more than 200 locations): 2 instances (staging and production) and 1 demo.
    • Deployment SMD (less than 200 locations): 1 instance production.

    Candidate Experience and/or Conversational ATS and/or Candidate Engagement:

    • Franchisee: 1 production instance. 

    Paradox Instance Types

    Production is the designated system of record containing the essential data that ensures the overall operational continuity of the system and where the integrity and validity of the data is critical.

    • Customers receive access to one Production instance for their organization.
    • All configuration is promoted from Staging  to Production manually at Go-live, and Production is not able to be refreshed.

    Staging is a non-production instance used to implement the Paradox Solution. This includes configuring features, testing, and building integration before deploying changes and loading customer data into the production environment.

    • Customers receive access to one Paradox Staging instance for their organization.
    • The Paradox Staging is exclusively designated for non-production use.
    • The cutover from Staging to Production may start several weeks before the go-live date.
    • Staging instances cannot be programmatically refreshed.
    • The Staging environment will remain active for the duration of the subscription agreement. Customers will continue to have access to Staging instance post deployment to build and test new features and configurations before moving into Production.
    • New features are pushed to Staging and Production on the same date.

    Demonstration is a non-production instance featuring Conversational ATS, pre-loaded with fictitious organizational data and a single test user account to simulate a real-world enterprise environment.

    • This instance is deleted 180 days after creation.

    Paradox Extend and Optimize

    For customers on the Production instance, the Staging instance is used to deploy Paradox products or functionality from future order forms. No additional instances will be provided.


    Instance Purchase or Renewal

    You can't purchase or renew extra instances.

    conversational ats integrated ats crm

    Was this article helpful?

    Yes
    No
    Give feedback about this article

    Related Articles

    • Employee experience completing a fillable PDF created within the Paradox platform
    • Paradox Assist: Add a candidate
    • Client Setup: Site Studio

    Copyright 2026 – Paradox.

    Knowledge Base Software powered by Helpjuice

    Expand