September 2026, 2.6.6 Release Notes
Updated at August 31st, 2026
Table of Contents
Happy September! 🎉 We've been working on updates to help your teams hire faster and smarter.
Here's the latest feature releases and improvements.
This September 8th release includes the following enhancements. These updates are subject to change until the day of the release.
The features in this release apply to your account based on your product packaging. Contact your CS Representative with any questions about use cases or account configuration.
Paradox Analytics
Journeys permissions, Job Search Conversion Rate metrics, and Advanced Shifts reporting
Advanced shifts reporting
Job Search Conversion Rate metrics
- Product: Platform
- Impacted features: Paradox Analytics (Reports, Dashboards)
- Enablement path: Automatic logic update
- Users impacted: All user roles who build or view Paradox Analytics reports and dashboards
You can now do the following in Paradox Analytics:
- See only what you're allowed to see. Reports respect Journey stage and status permissions, consistent with Journeys.
- Trust Job Search conversion metrics. Previously, applicants who never searched could be included, which could inflate conversion rates.
- Report on shift data. When Advanced Shifts is enabled, reports can include new shift fields for hiring analysis.
By giving your reporting team data that aligns with stage and status permissions in Journeys, reflects real job search behavior, and includes shift details for hiring, your organization can make decisions from accurate reports instead of manual workarounds outside Paradox.
Setup and activation
What you need to do
No setup is required. This feature is automatically available.
Additional information and limitations
Journey stage and status permissions
- Journey permissions apply to Candidate Journey Status, Candidate Wide, Assessments, Talent Community, Campaigns, Interviews, Candidate Surveys, User Surveys, Care Messages, Candidate User Forms, and Events system template reports.
- Journey stage and status permissions take priority over Job and Location permissions.
Job Search Conversion Rate
- Before the fix, Applications Through Job Search could count applicants who never searched, which made the rate unreliable (sometimes over 100%). Now both metrics (Applications Through Job Search and Job Search Conversion Rate in the Candidate Journey Status reporting category) only count candidates who did both: searched first, then applied.
- Saved reports and scheduled report exports may show the previous calculation until they refresh or run again.
Advanced Shifts
- Learn more about the advanced shifts fields available at Paradox Reporting Fields and Metrics.
Candidate Inbox
Simplified default segments and combined filters
- Product: Platform
- Impacted features: Candidate Inbox
- Enablement path: Automatic logic update
- Users impacted: All user roles with access to the Candidate Inbox
You can now do the following in the Candidate Inbox:
- Navigate a simplified default folder list with only View by Job, Action Needed, and All Candidates folders.
- Filter candidates in the Action Needed folder using the same filter experience as the All Candidates folder.
- Recreate views from the removed default folders using new filters.
By replacing redundant default folders and unlocking new filter possibilities, your team can narrow candidate lists faster on Action Needed and find every candidate without checking multiple folders.
Setup and activation
What you need to do
No setup is required. This feature is automatically available.
- Navigate to the Candidate Inbox.
- Using the left pane, select Action Needed, and select the filtering icon.
- In the filtering modal, select the desired filters. You can select the following new filters:
- Candidate Opt-Ins (Job Alerts and Job Search)
- Q&A (Candidate Q&A and Employee Q&A)
- Spam (Yes, candidate is marked as spam and No, candidate is not marked as spam)
- Unsubscribed (Yes, candidate is unsubscribed and No, candidate is not unsubscribed)
- Unknown Candidates (Yes, candidate is unknown and No, candidate is not unknown)
Additional information and limitations
- Removed default folders are available as filters so you can recreate the same candidate view.
- After selecting All Segments using the left pane, the More dropdown now only displays the View by Job folder.
- If a user's homepage was set to a removed folder, Paradox redirects them to the Candidate Inbox.
Conversational Events
Ability to change the event name per occurrence for recurring events
- Product: Conversational Events & Campus
- Impacted features: Recurring events
- Enablement path: Automatic logic update
- Users impacted: User roles who create and manage events (recurring events)
You can now customize event names (both internal and public) for individual event occurrences within a recurring event, so each date can reflect a unique title.
By letting you customize the title for each event occurrence, your event's team can keep recurring events organized without creating separate one-off events or relying on manual communication outside of Paradox.
Setup and activation
What you need to do
No setup is required. This feature is automatically available.
- Navigate to Events.
- Using the left pane, select Recurring Events.
- Open the desired recurring event.
- In the upper-right corner, select the settings icon, and then select Edit Event Occurrence.
- Edit the Public Event Name and Internal Event Name for that occurrence.
- Note: You can also select Internal Event Name is the same as Public Event Name to standardize both event names.
- In the upper-right corner, select Next.
- Save your changes to the recurring event.
Additional information and limitations
- Event occurrence-level names apply to that date only and do not change names for other dates in the series.
Data Privacy
Self-service email routing for deletion and modification requests
- Product: Platform
- Impacted features: Company Information
- Enablement path: Configure data privacy request email recipients in Company Information
- Users impacted: All user roles with access to Company Information (Paradox Admins only)
You can now configure who receives candidate data deletion and modification request emails. You can set multiple email recipients for both candidate data deletion and modification requests.
By putting data privacy request email routing in your team's hands, your organization can direct data privacy requests to the right contacts.
Setup and activation
What you need to do
Setup is required. This feature is automatically available to configure.
Contact your CS Representative for help configuring this feature.
If you don't change anything
Data privacy request routing continues using your account's existing setup.
Additional information and limitations
- Deletion and modification requests can be sent to the same recipient. You can set multiple recipients (email addresses) to receive the deletion and modification requests.
- Notification emails include CEM and public account identifiers so email recipients know which account the request applies to.
Job Management
Private jobs
- Product: Job Management
- Impacted features: Job Manager Settings (Private Jobs), Job Builder, Job Approvals, My Jobs
- Enablement path: Enable Private Jobs in Job Manager Settings (account-level) or enable Private in the Job Builder (job-level)
- Users impacted: All user roles with access to the Job Manager, My Jobs, and Job Approvals
You can now enable Private Jobs at the account level in the Job Manager Settings, mark a job as Private when you create a job or during a job approval, and copy a private posting link from My Jobs to send the job posting page to candidates for that role.
By keeping private recruiting separate from your public job listings, your team can fill invite-only roles without posting them to your career site or job boards.
Setup and activation
What you need to do
Setup is required. This feature is automatically available to configure.
Company/Account Admins:
- Navigate to the Job Manager.
- In the lower-left corner, select Job Manager Settings.
- Navigate to the Job & Templates section.
- Enable or disable Private Jobs to set it at the account level.
- Note: This setting is enabled by default for existing accounts and disabled by default for new accounts.
Users creating or editing jobs in the Job Builder and My Jobs (when Private Jobs is enabled):
- Navigate to the Job Manager or Approvals.
- Open an existing job, or create a new job.
- In the Overview step, enable the following settings as needed:
- Private
- Allow employees to edit the Private setting in My Jobs
- In the upper-right corner, select Save.
- Publish the job.
Users sharing a private posting link:
- Navigate to My Jobs.
- Select the action menu, or ellipses, to the right of the toggle.
- Select Copy External Private Posting Link to copy the link to your clipboard.
If you don't change anything
Jobs continue to post publicly as they currently do.
The Private setting is enabled at the account-level by default for existing accounts and disabled at the account-level by default for new accounts. Ensure to not enable the Private setting in the Job Builder if you don't want this functionality.
Additional information and limitations
- The former Confidential setting in Job Manager Settings has been renamed to Private Jobs.
- The Private setting is enabled by default for existing accounts and disabled by default for new accounts.
- New jobs have the Private setting and Allow employees to edit the Private setting in My Jobs disabled by default. Existing jobs have the Private setting disabled and the Allow employees to edit the Private setting in My Jobs enabled by default.
- Mobile app support for private jobs and the new private_job standard job attribute in System Attributes follows in a later release.
Apply job description section headers and footers to existing jobs
- Product: Job Management
- Impacted features: Job Description Sections, Job Builder
- Enablement Path: Configure a Job Description Section default placement to Header or Footer
- Users Impacted: All user roles with access to Job Description Sections and Job Builder (Job Manager)
You can now save a Job Description Section and apply it to all existing jobs that match the section's targeting rules, not only to new jobs created after the save. When you choose Save and Apply to All Jobs, Paradox shows how many jobs will be affected and applies updates in the background.
By extending section placement and targeting to existing jobs in one action, your team can roll out header, footer, and required section changes across your job catalog without updating each job manually.
Setup and activation
What you need to do
Setup is required. This feature is automatically available to configure.
Users managing Job Description Sections (Job Builder):
- Follow the navigation instructions in Dynamic job description overview and configuration instructions in Dynamic job descriptions: Configuration guide.
- Open an existing or new Job Description Section, and then select the settings icon.
- For Mark as Required, select between the following options:
- Required for all job descriptions
- Required for targeted job descriptions
- For Default Placement, select between the following options:
- None
- Header
- Footer
- In the lower-right corner, select Update.
- 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.
-
Apply to New and Existing Jobs: This section will automatically apply to existing jobs that match, as well as any newly created jobs.
- Note: This impacts the number of existing jobs in the account.
- Select Save to apply the section settings, and then select Save for the Job Description Section.
If you don't change anything
Job Description Sections with a header and footer default placement continue to apply only to new jobs until you select Apply to New and Existing Jobs.
Additional information and limitations
- If you select Not Required for the Mark as Required field or None for the Default Placement field, then this enhancement does not apply.
Prevent duplicate job categories from integrated job feeds
- Product: Job Management
- Impacted features: Data Feeds, Job Manager
- Enablement path: Automatic logic update
- Users impacted: All user roles with access to Data Feeds (job feeds) and the Job Manager
You can now rely on Paradox to match your integrated job feed's job categories to existing job categories when they are a one-to-one match, instead of creating duplicate categories with the same name.
By assigning jobs from the feed to the matching existing category, your hiring team keeps job organization consistent in the Job Manager.
Setup and activation
What you need to do
No setup is required. This feature is automatically available.
Additional information and limitations
- Paradox merges job categories only when the job feed's job category is a one-to-one match with an existing job category. When job category names differ across languages or job category names do not fully match, Paradox may still create separate job categories.
Platform
Mask PII in alert messages
- Product: Platform
- Impacted features: Alert Management
- Enablement path: Automatic logic update
- Users impacted: All user roles who receive alerts/notifications through channels (web, email, SMS, push notifications, Microsoft Teams
You can now rely on Paradox to enforce candidate attribute masking across additional Alert Management notifications. When an alert includes candidate data, users see only the information their user role is permitted to view, regardless of delivery channel. This includes email subjects, SMS, push notifications through the Paradox app, web alerts, and Microsoft Teams.
By extending masking across outbound alert channels, your organization closes data privacy gaps and reduces the risk of exposing PII to unauthorized users.
Setup and activation
What you need to do
No setup is required. This feature is automatically available.
- Navigate to the channel where you receive alerts (web, email, SMS, push notifications, Microsoft Teams).
- Open an alert that includes candidate profile data.
- Note: Masked values display as **** when you do not have full access to the System Attributes > Attribute Visibility > Candidate Profile permission.
Additional information and limitations
- This release applies masking candidate information (candidate/lead attributes) to the following alert types:
- Candidate Request Alerts
- Scheduling Alerts
- Web Alerts
- Candidate Message Alerts
- Candidate Survey Alerts
- Note Alerts
- Workflow Alerts
- Email subject lines that include candidate profile data
- A previous release applied masking candidate information (candidate/lead attributes) to the following alert types:
- Candidate Submission Alerts
- Smart Alerts
- Share Alerts
- Care Alerts (Candidate Experience Alerts) for Basic/Limited Users, including Candidate Requests and Candidate Surveys
- Masking candidate information (candidate/lead attributes) follows permissions in Roles and Permissions. Contact your CS Representative for help configuring access to permissions.
- In a future release, users with View Access will be able to click an eye icon to unmask system attributes in alerts.
- In this release, the rest of the alert types that haven't been listed are not supported.
New Assist permissions (calendars and custom email alerts) in Roles and Permissions
- Product: Platform
- Impacted features: Roles and Permissions, Assist (calendars and custom email alerts)
- Enablement path: Grant or restrict access to the Assist permission in Roles & Permissions
- Users impacted: All user roles with access to Assist
You can now grant or restrict access to Assist using a dedicated Assist permission with full access, view access, and no access levels.
By adding an Assist permission, your team can grant System Implementers (SIs) and any other user role the access they need to complete Assist calendar and email configurations.
Setup and activation
What you need to do
Setup is required. This feature is automatically available to configure.
Contact your CS Representative for help configuring this feature.
If you don't change anything
Users with no access to the Assist permission cannot view the Calendar or Custom Email Alerts from the Assist page. Users with view access to the Assist permission can only view the Calendar or Custom Email Alerts from the Assist page.
Outbound message content restriction and compliance filtering
- Product: Platform (Communications and Compliance)
- Impacted features: Messaging Channels (across platform - including Employee Communications)
- Enablement path: Automatic logic update
- Users impacted: All user roles with access to configure or send outbound messaging to candidates
You can now rely on Paradox to block outbound messages that contain prohibited content before they are saved or sent to candidates and employees. When a message violates messaging compliance rules, Paradox stops the action and prompts the sender to update the text.
By enforcing compliance at the point of delivery, your organization reduces legal risk, protects messaging channel deliverability from carrier penalties, and keeps prohibited content from reaching recipients.
Setup and activation
What you need to do
No setup is required. This feature is automatically available.
Additional information and limitations
- Paradox checks message text in the following situations for SMS, WhatsApp, Email, and Web channels:
- When a user sends a message in the Candidate Inbox, Employee Communications Inbox, or the Messages app
- When a user saves message text in areas such as Workflows, Campaigns, Messaging Templates, and Conversation Builder.
- If prohibited content is found, Paradox blocks the sent/save action and displays the following message: "This message contains content that violates messaging compliance rules. Please update the message and try again."
- This feature supports the following languages: English, Spanish, Portuguese, and French.
- Paradox does not check automated system messages, unedited AI responses, WhatsApp template settings, uploaded files, or lookup table values.
Manage custom source values
- Product: Platform
- Impacted features: Source Tracking
- Enablement path: Automatic logic update
- Users impacted: All user roles with access to Source Tracking
You can now build and maintain your own source library in Source Tracking, so your team can attribute candidates to the sourcing channels your organization actually uses instead of a fixed system list.
By giving your organization its own source library, your team can trust Source Tracking reports when measuring which recruiting channels perform best, assign sources more accurately at the point of entry, and add missing channels on your own instead of waiting for Paradox Support to update the list.
Setup and activation
What you need to do
No setup is required. This feature is automatically available.
- Select the All Apps menu in the upper-left corner of the header and then Settings in its drop-down menu.
- When the Settings page opens, select Source Tracking under the Platform section.
- Using the left pane, select Source Management.
- Complete the following actions as needed:
- In the upper-right corner, select + Add New Source to create a new source.
- In the Source Management list view, select an existing source.
- In the Add New Source or Edit Source drawer, update the following details:
- Enter a Name for the source.
- Select + Add Alias to optionally add an alias so UTM values from different partners map to the same source.
- In the lower-right corner, select Save or Create.
Additional information and limitations
- Source names and aliases must be unique within the account (case-insensitive).
- You can set a maximum of 10 aliases for a source.
- When candidates apply through a tracked link, Paradox still assigns Source from that link even if recruiters cannot edit Source on candidate profiles.
- In this release, bulk import, export, and merging two source values into one isn't supported.
Scheduling
User calendar time format setting (12-hour or 24-hour)
- Product: Scheduling
- Impacted features: Calendar Settings (in My Calendar/Calendars or Roles and Permissions)
- Enablement path: Configure user communications time format in Calendar Settings
- Users impacted: All user roles with access to Roles and Permissions
You can now set a personalized 12 hour or 24 hour time format for your scheduling user communications in your Calendar Settings. Your time format defaults to your organization's account setting, but you can customize it at any time.
This feature eliminates scheduling confusion for global teams by ensuring consistent, localized time displays across all scheduling user communications.
Setup and activation
What you need to do
Setup is required. This feature is automatically available to configure.
You can access this feature through the Calendar Settings in Roles and Permissions or My Calendar/Calendars.
Users with access to Calendar Settings in Roles and Permissions
To configure user communications time format:
- Select the All Apps menu in the upper-left corner of the header and then Settings in its drop-down menu.
- When the Settings page opens, select Roles and Permissions under the Permissions section.
- Using the left pane, navigate to Employees, and select the desired user role.
- Select the desired user.
- Under Calendar Connection and Details, navigate to the User Communications Time Format setting.
- Select between the following time format options:
- 12 hour
- 24 hour
- In the lower-right corner, select Save.
Users with access to Calendar Settings in My Calendar/Calendars (Interview Settings)
To configure user communications time format:
- Select the All Apps menu in the upper-left corner of the header and then My Calendar/Calendars in its drop-down menu.
- When My Calendar/Calendars opens, select the action menu, or ellipses, and then select Calendar Settings.
- From the Interview Settings section, navigate to the User Communications Time Format setting.
- Select between the following time format options:
- 12 hour
- 24 hour
- In the upper-right corner, select Save.
If you don't change anything
Your employees continue to see the time format at the account level from the Default Time Format setting in the Scheduling section of Client Setup.
Unless customized, employees continue to use the account-level time format set from the Default Time Format setting in the Scheduling section of Client Setup.
Additional information and limitations
- The user's time format applies to scheduling user communications that include time-based information, including Assistant Messaging, User Workflows, and other areas that use time format tokens.
- Users who manually set a time format keep their selected time format when the time format setting is adjusted at the account level.
Minor enhancements
Minor enhancements are documented on the day of the release. Check back later!
Helpful release links
- Coming soon!