• Role Impact: By default, this feature impacts Paradox Admins and System Implementors (Partner Users), as well as user roles with access to Client Setup. This also impacts candidates, who can view verification code delivery options after the Secure Login page. 
• Feature Activation: This feature is automatically available to use for all customers. Setup is required. Only users with full access to Client Setup can configure the verification code options. If needed, contact your Company/Account Admin or CS Representative for assistance. To enable verification codes using the candidate's primary contact method:
  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 Client Setup under the Paradox Tools section.
  3. Client Setup will then open. Scroll down to and open the More section from the left panel.
  4. Enable Verification Code Primary Contact Method.
     • By default, this is disabled. When enabled, candidates will only be sent two-factor authentication (2FA) via their primary contact method. 
  5. In the lower-right corner, select Save to apply changes. 

• Role Impact: By default, this feature impacts Paradox Admins and Account Admins, as well as user roles with access to the Content Management System (CMS).
• Feature Activation: This feature is automatically available to configure for all customers using the CMS. Only users with full access to Client Setup can configure the Check Status experience. If needed, contact your Company/Account Admin or CS Representative for assistance. To disable the Check Status experience: 
  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 Client Setup under the Paradox Tools section.
  3. Client Setup will then open. Scroll down to and open the Q&A section from the left panel.
  4. Disable Candidate CheckStatus Experience.
     • By default, this setting is enabled.
  5. In the lower-right corner, select Save to apply changes.  

• Role Impact: By default, this feature impacts Account Admins, as well as user roles with access to the Content Management System (CMS) and Content Quality Score. 
• Feature Activation: This feature is automatically available to use for all customers using Content Quality Score (a CMS feature, with a Contextual AI add-on). No setup is required with this automatic logic update. To access the Content Quality Score:
  1. Follow the configuration and navigation steps in Content quality score. 
  2. View the Content Quality Score.
     • Note: You must have five configured intents to receive the Content Quality Score.
  3. Select Improve Score to review the flagged responses and improve your Content Quality Score.

• Role Impact: By default, this feature impacts Account Admins and Power Users, as well as user roles with access to the Event Builder.
• Feature Activation: This feature is automatically available to use for all customers using Conversational Events. Superday Events is on by default and can be turned off in the Conversational Events section of Client Setup. Confirm Superday Events is enabled in Client Setup before you create a Superday event. To create a Superday event:
  1. Follow the navigation steps in Create an event.
  2. In the Overview step, enable Is this a Superday event?
     • Important Note: Once candidates are registered and scheduled to this event, the Superday toggle cannot be turned off.
  3. Edit the amount of candidates that can be registered and scheduled to the Superday event (maximum: 150).
  4. In the Schedule step, build the event's interview sessions. Superday sessions run consecutively and can't be scheduled over one another.
  5. In the Registration step, select Invitation only private event.
     • Note: Superdays are typically private. This means candidates cannot join via the Event Phone Number or Event Landing Page. They can only access this event through auto-scheduling via a Workflow trigger or manual scheduling from the Candidate Inbox.
  6. Complete the remaining steps for the event.
  7. In the upper-right corner, select Create Event.

• Role Impact: By default, this feature impacts Paradox Admins and System Implementers (Partner Users), who configure this feature. It also impacts Power Users (recruiters and hiring managers) and Basic/Limited Users, who use My Calendar/Calendars.
• Feature Activation: This feature is automatically available to use for all customers using Scheduling. Setup is required to configure a default calendar for a user role. Contact your CS Representative for help configuring this feature.

• Role Impact: By default, this feature impacts Paradox Admins, System Implementors (Partner Users), and Account Admins with access to building Forms and Offers. 
• Feature Activation: This feature is automatically available to use for all customers using Forms (adding conditions to form sections) or Offers (adding a dropdown component and field mapping to list-select system attributes). No setup is required with this automatic logic update. 

• Role Impact: By default, this feature impacts Paradox Admins, System Implementors (Partner Users), and Account Admins with access to Workflows and Journeys (Next Steps), who configure this behavior. It also impacts Power Users (recruiters and hiring managers), who manage Offer Approvals from the Candidate Inbox.
• Feature Activation: This feature is automatically available to use for all customers using Offer Approvals. Setup is required to configure offer approvals that don't send automatically. 

To configure offer approvals that don't send offers automatically (Paradox Admins, Account Admins):

1. Follow the navigation and configuration instructions to create a workflow/open an existing workflow in Workflows.
2. Using the left pane, navigate to Offer > Offer Approval Approved.
3. Select the action menu, or ellipses, and select Delete to remove the Move Status to > Send Offer action type.
4. Follow the configuration and navigation instructions in Create next steps in Journeys.
5. Using the left pane, navigate to Offer > Offer Approval Approved.
6. Select + Add Next Step Button.
7. Customize the Button Title and select + Select Status.
8. Select Send Offer, then Apply.
9. In the lower-right corner, select Save. 

To deliver an offer manually (Power Users, like Recruiters and Hiring Managers):

1. In the Candidate Inbox, select Send Offer from the Next Steps to move the candidate forward.

• Role Impact: By default, this feature impacts all user roles.
• Feature Activation: This feature is automatically available to use for all customers using Employee Communications (accounts with Employee Communications enabled only, Paradox Franchise users/accounts). No setup is required with this automatic logic update. 

• Role Impact: By default, this feature impacts Paradox Admins and System Implementers (Partner Users), as well as user roles with access to the Integration Center. 
• Feature Activation: This feature is automatically available to use for all customers using the Integration Center. No setup is required with this automatic logic update. 

• Role Impact: By default, this feature impacts Paradox Admins, as well as any user role with access to Job Description Sections in the Job Manager. It also impacts Account Admins, as well as any user role with access to the Job Builder (Job Description step).
• Feature Activation: This feature is automatically available to use for all customers using Job Management (with Job Description Sections enabled). Setup is required to set a section's default placement. To configure the section's default placement:
  1. Follow the navigation instructions in Dynamic job description overview and configuration instructions in Dynamic job descriptions: Configuration guide.
  2. Open an existing or new Job Description Section, and then select the settings icon.
  3. For Default Placement, select between the following options:
     • None
     • Header
     • Footer
  4. In the lower-right corner, select Update.
  5. If you select Header or Footer, apply the section settings from the following options:
     • Apply to New Jobs: This section will automatically apply to new jobs created from this point forward. Existing jobs must be manually updated and published to include this section.
  6. Select Save to apply the section settings, and then select Save for the Job Description Section.

• Role Impact: By default, this feature impacts Paradox Admins, System Implementors (Partner Users), and Account Admins with access to Journeys, who configure this behavior. It also impacts Power Users (recruiters and hiring managers), who move candidates to statuses from the Candidate Inbox.
• Feature Activation: This feature is automatically available to use for all customers using Journeys. No setup is required to maintain existing permissions for stage types already covered. Setup is required to configure permissions for newly supported stage types. To configure permissions for a stage:
  1. Follow the navigation and configuration instructions in System Journeys overview and Create a new Candidate Journey.
  2. Open the desired Journey.
  3. Select the desired stage, and then select Edit Permissions.
  4. Using the left pane, select the desired Stage Permissions, Status Permissions, or Action Needed Permissions (if Highlight this step as Action Needed for employees is enabled) as needed.
     • Note: Action Needed permissions require Full Access to the relevant stage or status.
  5. Set the permission level for each employee role, hiring team role, or individual employee for a stage or status:
     • Capture, Survey, Form, Application, Offer, Onboarding, Background Check, and Conversation stages:
       • Full Access: Employee can view and manage candidates.
       • View Access - Full: Employee can view candidates, including form/offer details and conversation/survey messages.
       • View Access - Limited: Employee can view candidates, but cannot see form/offer details or any conversation/survey messages.
       • No Access: Employee cannot view or manage candidates.
     • All other stage types (Scheduling, Hired, Disposition, Event, Superday Hiring Event, Orientation Event, Custom):
       • Full Access: Employee can view and manage candidates.
       • View Access - Full: Employee can view candidates, but cannot manage them.
       • No Access: Employee cannot view or manage candidates.
  6. In the upper-right corner, select Save Changes.

• Role Impact: By default, this feature impacts Account Admins, as well as any user role with access to Location Management (Location Mapping) and who upload job feeds.
• Feature Activation: This feature is automatically available to use for all customers using Location Management. No setup is required with this automatic logic update. 
  • When Paradox detects a job that has moved from a Tentative Location to a Formal Location, you can review the suggested merge in Location Management and confirm or deny it. Confirming a merge reassigns every candidate still associated with the Tentative Location to the matching Formal Location.

• Role Impact: By default, this feature impacts all user roles with access to Paradox Assist, except Basic/Limited Users. 
• Feature Activation: This feature is automatically available to use for all customers using Paradox Assist. No setup is required. Users can add candidates through Assist when both of the following are in place:
  • Olivia Assist, Contextual AI are enabled in Client Setup.
  • Contextual AI - Olivia Assist & Generative Platform Experience is enabled in Company Information.
  • Disable Adding a Candidate Manually is not enabled in Client Setup.
  • The user has the Full Access permission level to the Candidates > Add Candidate permission in Roles & Permissions.

Channels

• We've added Norwegian and Finnish as language options when creating and editing WhatsApp templates in the WhatsApp Admin Page, and added Norwegian and Finnish text to the universal WhatsApp templates.

Hiring Events

• We've updated the Close Pre-Event Registration logic based on the session types configured in the hiring event:
  • Event is Sessions Only: When the Total Registered Candidates setting is set to Set Specific Number, registration closes once the total number of registered candidates reaches that limit. The At Set Time setting is unchanged.
  • Event Interview Sessions Only: When the Total Registered Candidates setting is set to Max interview slots available, registration closes once all interview slots are filled or scheduled. When set to Set Specific Number, the limit cannot exceed total available interview slots, and registration closes once that number of interview slots are scheduled.
  • Event Sessions + Event Interview Sessions: When the Total Registered Candidates setting is set to Set Specific Number, registration closes when total candidate registrations reach the set number, using the same logic as sessions-only events.

Integration Center/Integrations

• We've updated Advanced Webhook Inbound audit logs in the Integration Center with dedicated log screens, additional filters, customizable table settings, and saved filter templates. The table view displays Response Status, Request Name, Unique ID, and Date & Time.
• We've updated login and user management for accounts using the Workday UPAS integration:
  • Users sign in to Paradox through Workday rather than a separate Paradox login.
  • User profile fields for Workday-provisioned users are read-only in Roles & Permissions, since Workday is the system of record for that data.
  • Logging out of Paradox also logs the user out of Workday.
  • When a Workday session expires, Paradox redirects the user through the Workday sign-in flow.

Scheduling

• We've updated the Interviews page so the experience is consistent across desktop and mobile web, with enhanced filtering, column customization, segments, and segment deletion now available on mobile web.
• We've updated the Microsoft Teams app so users can switch between Production (US), Production (EU), Staging (US), and Staging (EU) by using the help command, with each user selecting their environment independently. Staging environments also now support the Teams communication channel.