What you need to do

No setup is required. This enhancement is automatically available to use.

User experience 

To access:

1. Navigate to the Browser Extension.
2. On the Login page, select Sign in with SSO.
3. Follow the instructions on the guided loading page.

Additional information and limitations

• Users must remain on the new login tab until the Browser Extension finishes loading. Once authenticated, the session will automatically sync across all other tabs.
• If the Browser Extension does not open automatically, users can initiate a session by selecting the Launch the Extension button or opening the Browser Extension from the browser toolbar on the new login tab.

What you need to do

Setup is required. This enhancement is automatically available to configure.

User experience (career site developers)

Only users with full access to the Code Editor in the Site Studio can configure the Job ID attribute in the Job Details URL. If needed, contact your Company/Account Admin or CS Representative for assistance.

1. Select the All Apps menu in the upper-left corner of the header and then Site Studio in its drop-down menu.
2. Select the desired site.
3. Select Edit Settings on the site dashboard.
4. Using the left pane, navigate to the Jobs section.
5. Under the Apply URL Destination section, use the dropdown menu to select the Job ID Attribute.
6. In the upper-right corner, select Save.

If you don't change anything

Job Detail URLs function as they do today.

Additional information and limitations

• The Job ID Attribute drop-down menu is only selectable if the Apply URL Destination drop-down menu is set to Job Details.
• You must select an attribute that actually exists on the site's jobs. For example, you cannot use Paradox Job ID on customer-job-only sites.
• Ensure to verify the feed type and test a sample job before updating a live site. Selecting the wrong attribute will break job links, sitemaps, and SEO rankings.

What you need to do

Setup is required. This feature is automatically available to configure.

User experience (career site developers)

Only users with full access to the Code Editor in the Site Studio can configure the Google location country restriction. If needed, contact your Company/Account Admin or CS Representative for assistance.

1. Select the All Apps menu in the upper-left corner of the header and then Site Studio in its drop-down menu.
2. Select the desired site.
3. Select Edit Code on the site dashboard.
4. Using the left pane, select Components.
5. Select the Jobs Search component.
6. Under the Location Field selection, select Advanced Settings.
7. Select a country using the Google Location Country Restriction dropdown menu. You can select up to five countries.
8. In the lower-right corner, select Confirm.
9. In the upper-right corner, select Save to ensure your site is saved.

If you don't change anything

If no countries are selected in the dropdown menu, all countries (worldwide) display in Google job search results.

Additional information and limitations

• This dropdown menu limits location suggestions as a candidate types in the search bar for jobs. It does not by itself filter which jobs display in search results.
• The Google Location Country Restriction dropdown menu can only be selected if the Type Ahead Source(s) dropdown menu is set to Google.

What you need to do

No setup is required. This enhancement is automatically available to use.

Additional information and limitations

• WhatsApp is rolling out the username feature by country on its own schedule. This means Paradox is ready before those changes affect your account. Learn more at this article.
• Conversations from the Conversation Builder with WhatsApp Supported enabled must include the Phone Number question. It cannot be removed or made optional. Paradox automatically adds it to existing WhatsApp-enabled conversations that do not already have it.
• A WhatsApp candidate can opt-in to hide their phone number at any time, so the same conversation may change from phone number to BSUID. 
• When an inbound WhatsApp message from a candidate does not include the candidate's phone number (for example they hid their phone number with a username), the AI Assistant asks for the phone number in the conversation and verifies it matches the candidate's WhatsApp account (BSUID). 
• This enhancement is not applicable to customers without WhatsApp enabled. 

What you need to do

Setup is required. This enhancement is automatically available to configure.

Only users with full access to the Phone Number Registration page can submit a 10DLC Registration Form. If needed, contact your Company/Account Admin or CS Representative for assistance.

Franchise accounts

1. Follow the navigation and configuration instructions in the Phone number registration form (10DLC) article.
2. In the Company Information section, enable the This registration is for a franchise toggle. 
3. Enter the Franchise Brand Name (Doing Business As)*.
4. Ensure to save. 

Public company accounts

1. Follow the navigation and configuration instructions in the Phone number registration form (10DLC) article.
2. In the Company Information section, select Public from the Company Status dropdown menu.
3. Enter the Stock Ticker.
4. Select the Stock Exchange using the dropdown menu.
5. Ensure to save.

If you don't change anything

Approved campaigns already in market continue to operate; new or updated submissions follow the new validation rules.

Additional information and limitations

• Franchise campaign text can state which brand the franchisee operates under, which addresses common carrier rejections for missing franchise context.
• When you enable the This registration is for a franchise business and enter the Franchise Brand Name (Doing Business As) field, carriers receive the brand context they often require, which can reduce rejections for missing franchise information.
• This enhancement is not applicable to customers who don't text U.S. phone numbers or customers whose brands registrations are already approved. Additionally, this enhancement only affects brand registrations submitted after this release. Brand registrations that are currently at an In Progress status may still require manual handling.

What you need to do

Setup is required. This feature is automatically available to configure.

Permission setup (Paradox Admins/System Implementers)

To grant/restrict access:

1. Select the All Apps menu in the upper-left corner of the header and then Settings in its drop-down menu.
2. When the Settings page opens, select Roles and Permissions under the Permissions section.
3. Using the left pane, select Roles and Permissions.
4. Select the action menu, or ellipses, for the desired user role, and then select Edit.
5. Navigate to the CheckStatus Configuration child permission under the Content Management System permission.
6. Grant/restrict access to the permission using the following access levels:
   • Full Access: Users can create, edit, and manage functionality on the CheckStatus Configuration page.
   • View Access: Users can view the CheckStatus Configuration page without creating, editing, and managing functionality.
   • No Access: Users cannot view the CheckStatus Configuration page; the contents are hidden from their view.

User experience (Company/Account admins)

Only users with full access to the CheckStatus Configuration section in the CMS can configure the status display for the Candidate CheckStatus experience.. If needed, contact your Company/Account Admin or CS Representative for assistance.

1. Select the All Apps menu in the upper-left corner of the header and then CMS in its drop-down menu.
2. Using the left pane, select CheckStatus Configuration.
3. Select the desired journey.
4. Update the Custom Content column for each status as needed. 

If you don't change anything

The CheckStatus experience continues to display the default content from the published journey to candidates.

Additional information and limitations

• The CheckStatus Configuration page shows the last published version of a journey. Unpublished journey edits in Journeys are not reflected until you publish the journey. 
• Default and custom journey statuses still default to Processing until any Custom Content is published.
• The access defaults in Roles and Permissions: Company/Account Admins have Full Access, while other user roles default to View Access unless you adjust the permissions

What you need to do

No setup is required. This enhancement is automatically available to use.

User experience (event managers/creators)

To access:

1. Follow the navigation and configuration instructions in the Create an event article.
2. From the Registration section, navigate to the Close Pre-Event Registration section as needed.
3. Using the At Set Time dropdown menu, select between the following options:
   • Event end date & time
   • 1 hour before the event
   • 12 hours before the event
   • 1 day before the event
   • 2 days before the event
   • 3 days before the event
   • 4 days before the event
   • 5 days before the event
   • Set specific date and time
4. From the Registration section, navigate to the Close On-Site Registration section as needed.
5. Using the At Set Time dropdown menu, select between the following options:
   • Event end date & time
   • 1 hour after the event
   • 12 hours after the event
   • 1 day after the event
   • 2 days after the event
   • 3 days after the event
   • 4 days after the event
   • 5 days after the event
   • Set specific date and time (custom selection)
6. Ensure to save the event.

Additional information and limitations

• The new registration options in the dropdown menu apply to hiring events, superday events, campus events, orientation events, and event templates.
• You can still customize when pre-event and on-site registration closes with the Set specific date and time option.
• Existing published events are unchanged until someone edits the close registration dropdown menus in the Event Builder.

What you need to do

No setup is required. This enhancement is automatically available to use.

What you need to do

No setup is required. This enhancement is automatically available to use.

User experience (integration specialists)

To access:

1. Follow the navigation and configuration instructions in the Integration Center overview article.
2. Select any integration request.
3. Make changes as needed, and then select Commit in the lower-left corner.
4. In the Commit Request modal, choose one of the following options to document your changes:
   • Generate a Comment: Automatically create a system-generated comment.
   • Custom Comment: Type your own description of the changes made in this version.
5. Select Confirm.

Additional information and limitations

• Paradox generates comment text only when you select Generate a Comment on the commit or restore modal. Generated text describes what changed, but it doesn't explain why.
• The first commit on a new integration may produce a short summary if there is no prior committed version to compare against.
• Commits that are confirmed with an empty comment field do not store a comment on that version.

What you need to do

Setup is required depending on your account configuration. This enhancement is automatically applied to accounts.

For accounts using Paradox Legacy job IDs (Unique and Version ID toggle currently OFF)

Work with your CS Representative to:

1. Identify where Job IDs are used today: Review your internal processes, reports, feeds, and integrations that reference Job IDs to understand where the ID is currently used and how the transition may affect the experience.                                                                                                 
2. Coordinate with your partners: Share this change with your external partners (agencies, career site provider, job boards like Indeed, etc.) so they can plan and implement any updates needed on their side. For example, agencies may need to make mapping updates to ensure jobs do not fall off from their connection.                                                                                                                            
3. Align on your transition timeline: Work with your Paradox team to confirm a transition date that best fits your organization and partners, ahead of the automatic opt-in date. 

For accounts already using Paradox Enhanced job IDs (Unique and Version ID toggle currently ON)

No setup is required. You can now count on a one-time, automatic restore of applicant Job IDs for candidates who applied before the Unique and Version Job ID toggle was first turned on in your account.

Additional information and limitations

• In a future release on December 8th, 2026 (for December's release, 2.6.9), Paradox plans to automatically enable the Unique and Version Job ID toggle for Conversational ATS accounts that do not have it enabled yet. 

What you need to do

No setup is required. This enhancement is automatically available to use.

Additional information and limitations

• If the Private Jobs toggle is not turned on in your account in the Job Manager Settings, the Private Job (private_job) attribute still displays and returns as False (not a blank value).

Channels

• We've updated the Verification Code Primary Contact Method toggle in Client Setup so the setting is enabled by default for all accounts. Candidates receive two-factor authentication (2FA) codes through their primary contact method when this toggle is enabled.

Events and Campus

• We've updated the slide-out drawer for candidates registered or scheduled to hiring event interview sessions, superday hiring events, and orientation events so the Cancel and Reschedule buttons are visible without needing to expand the interview summary.

Paradox Analytics

• We've updated candidate survey reporting in Analytics and Reporting to the Candidate Surveys entity:
  • A new Overall Survey Summary system-wide template is available when building reports.
  • You can add Candidate Survey Responses: Satisfaction Point and Candidate Survey Responses: Is Excluded From Satisfaction as report fields.
  • You can add Survey Value (1) through Survey Value (5), Unique Candidates Engaged, and Satisfaction Rate, Dissatisfaction Rate, and Neutral Rate as metrics.
  • Rate metrics count only scored, rating-style answers. Open-ended and CMS-excluded questions are not counted.
• We've updated user survey reporting in Analytics and Reporting to the User Surveys entity to include candidate evaluation survey responses.
• We've updated reporting in Analytics and Reporting so you can report on the UUID candidate ID format.

Candidate Inbox

• We've updated Layout Settings for segments in the Candidate Inbox so you can save segment order and Home segment defaults without errors from users who no longer have access.

Content Management System (CMS)

• We've updated Content Quality Score in the CMS so your account score only drops for intents listed as flagged in Improve Score, persona intents no longer affect the score, and every user on the account sees the same score.

Knowledge Training Library

• The default access level for the Knowledge Training Library child permission (under the Content Management System > Candidate Assistant Responses child permission) is now set to full access for Company/Account Admins, matching current access level to other CMS features.

Paradox Assist

• The Olivia Assist toggle in the Olivia Assist section of Client Setup now defaults to automatically enabled for all new accounts. This update supports the transition from legacy Assist to Paradox Assist. Existing account configurations remain unaffected.