About this Guide

This guide is designed to help Crelate System Administrators understand the potential user impact of an upcoming release of Crelate. The guide provides additional insights that Crelate System Administrators should be aware of. Crelate provides this guide ahead of scheduled releases to allow Crelate System Administrators time to prepare for and take advantage of new or changing system capabilities.

About Crelate Upgrades

All upgrades to Crelate are automatic, benefit all users and typically require no user action. However, not all system upgrades are on by default. System Administrators may need to opt-in or opt-out of some new functionality. We know change can be disruptive, and we work hard to ensure System Administrators have the flexibility to control when new features are available to their teams.

EEOC, OFCCP and VEVRAA Compliance Surveys – Changed

Impact	EEOC, OFCCP and VEVRAA surveys can now be enabled independently, where previously one survey depended on another being turned on. Pre-Hire and Post-Hire Compliance toggles have been added to de-couple that choice from the EEO survey. Disability, veteran and consent questions no longer arrive with an answer preselected on the candidate’s behalf. Whether compliance questions appear is now determined by the job’s country record rather than a text match on the location. Disability and EEO copy is being updated across the Jobs Portal, Indeed screening, Employee Portal onboarding, and Reports.
Severity	Medium
Applies To	All organizations running compliance surveys. Federal contractors in particular.
Action Required	None required. Because surveys no longer depend on one another, we recommend a quick review of your compliance settings after the release to confirm each survey is enabled as you intend. Recent court rulings have resulted in major changes here, and all clients are advised to consult their own legal counsel before using these features.
SKU	Business and Higher for pre-hire surveys. Hire module for post-hire surveys

Report Editing Permissions – Changed

Impact	Only a report’s owners and Admins can edit, rename, delete, or save a report. Users who previously had full report access but do not own a report now see it read-only and can use Save as to create their own copy. Built-in reports (Activities, Candidates, Jobs, Placements, and Compliance) have no owner, so only Admins can change them. Report owners with limited report access now see every page of the reports they own.
Severity	High
Applies To	All organizations where non-Admin users edit shared or built-in reports.
Action Required	Identify the people who maintain your shared reports and make them owners. After the release, review the Private Reports list to find reports without an owner.
SKU	Business Plus and Higher

Reporting Data Consistency – Changed

Impact	Date ranges now resolve against the correct user or organization time zone, including daylight saving time, so revenue, placements, custom date fields and scheduled reports land in the period they belong to. Reports can also return more data, keep the largest contributors when a result set must be shortened, and show an error message if a query cannot be completed. Inactive and deleted owners are handled consistently, and inactive user groups can be grouped or hidden. Records owned by deactivated users appear in an Inactive users group, records owned by deleted users appear as No longer a user, and records with no owner appear in a No owner group. Values beyond a chart’s display limit are grouped into Other. These records were previously left out, so totals on charts grouped by user or owner may increase and pie chart percentages may shift. Filters on date-only fields (start, due, and custom dates) now use the user’s calendar day, which can change counts at the start and end of a period. Page filters now apply to the record type each chart counts. Page filters and chart filters now combine consistently on every chart: the page filter applies first, and chart filters narrow results further.
Severity	High
Applies To	All users who build, view or schedule reports.
Action Required	None required. Some figures may shift slightly after the release resulting in more reliable figures. If your team relies on reports for commissions, forecasts, or board reporting, we recommend letting those stakeholders know ahead of time. Review your reports, charts, and any scheduled reports. Compare key charts grouped by owner or user before and after the release. If a total went up, check the new Inactive users, No owner, or Other groups. To see where page and chart filters are set and how they combine, read Configuring Reports, Pages, and Charts.
SKU	Business and Higher

Scheduled Report Emails – Changed

Impact	Scheduled report emails now use the time zone of the person who set up the schedule, then the organization’s time zone, then Pacific time. The default for users with no time zone changes from Eastern to Pacific, so their emails may arrive up to three hours later and “today” or “yesterday” ranges may cover a different day. A footer names the time zone used. Emails scheduled from a duplicated page now use that page’s charts and filters. Charts that fail to load are left out of the email instead of sent empty.
Severity	Medium
Applies To	All users who send or receive scheduled report emails.
Action Required	Confirm that users who set up scheduled emails have their time zone set. Recipients who rely on emails for daily or end-of-day numbers should check the first few after the release.
SKU	Business and Higher

Report Privileges in User Roles – Changed

Impact	Report privileges in the User Roles editor have been regrouped. Full report access no longer includes scheduling report emails or access to all reports; these are now separate privileges.
Severity	Medium
Applies To	Administrators who manage User Roles.
Action Required	After the release, review the report privileges on each role and confirm scheduling and report access are set as you intend before saving any role changes.
SKU	Business and Higher

Reporting Chart Defaults – Changed

Impact	New single number charts default to the modern style, and charts apply gradients by default. Charts also gain refreshed color themes and fill patterns, which improve both downloading and accessibility patterns. Funnel segments are now sized by value, so existing funnels change shape. In pivot tables, empty and zero cells display a dot (·), heat shading is on by default, and up to 4,000 rows can be shown. Reconciliation reports keep their saved names, so a title may show an older date unless the report is set to update automatically; the report’s data still rolls forward.
Severity	Medium
Applies To	All users who build or view reports.
Action Required	None required. If you prefer the previous look, both the modern style and the gradients can be turned off. Please note this is done on a per chart basis. There is no global setting to revert all charts at once.
SKU	Business and Higher

Compliance Report Name – Changed

Impact	The built-in EEOC report is renamed Compliance in every organization that has not already renamed it.
Severity	Low
Applies To	Organizations that use the EEOC report.
Action Required	None required. Update any internal training or links that refer to the EEOC report by name.
SKU	Business and Higher

Crelate Search Assistant – New, On By Default

Impact	A new Search Assistant appears in Search. It suggests adjacent job titles to broaden a search and skills to narrow one. It is enabled by default.
Severity	Medium
Applies To	All users on Business plans and above.
Action Required	None required. Your users will see the Search Assistant appear after the release. Administrators can turn it off for the organization, and individual users can turn it off for themselves. It is part of Copilot and does not consume AI credits.
SKU	Business and Higher

API Default Page Size – Changed

Impact	The default number of records returned per request on API list endpoints increases from 50 to 100. The maximum you can request in a single call increases from 100 to 200.
Severity	Medium
Applies To	Organizations with integrations that call Crelate API list endpoints without specifying a limit.
Action Required	Review your integrations before the release. If an integration always specifies a limit, nothing changes. If it relies on the default, for example by stepping through pages in increments of 50, treating a response of fewer than 50 records as the last page, or sizing buffers and timeouts around a 50-record payload, those requests will now return up to 100 records each. To keep the previous behavior, pass limit=50 on your requests. If you are paging through 1000’s of records, larger page sizes can reduce the overall time and load required to get through the dataset. It is always recommended to specify the exact fields you need to reduce load and speed up calls. This is especially important when asking for larger page sizes.
SKU	Business and Higher

API Error Responses – Changed

Impact	API errors for bad requests now name the parameter that failed and, where known, what is allowed.
Severity	Low, but potentially breaking for integrations that depend on an undefined status returning an empty list.
Applies To	All API Users
Action Required	If you filter contacts or companies by status, make sure each value is one of your organization’s statuses. If you parse error message text, switch to the new error type and parameter name.
SKU	Business and Higher

Before this change, a bad request returned a message you had to read and interpret. Now every validation error includes a stable error type (such as InvalidSortAttribute or ParameterOutOfRange) and the name of the parameter that caused it. When the valid choices are known, the error lists them. The error types will not change once released, so your integration can safely match on them.

What the new errors cover

Sort field, sort direction, and fields entries that don’t exist. The error lists what you can use.
Values that can’t be read as the expected type, or that fall outside an allowed range. limit and offset are examples, and the error gives the minimum and maximum.
Values that aren’t one of the accepted choices.
Query parameters or request body fields the endpoint doesn’t recognize. These are reported instead of silently ignored.

Contact and company retrieves

These now report problems with filter operators, record types, and statuses in the same format.

Status values are checked against your organization’s own statuses. The error lists the valid ones.
Conflicting date filters are named. If you send both a modified date filter and a last-activity date filter, the error names the two that clash.

What to watch for

An undefined status on a contact or company retrieve used to return an empty list. It now returns a 400 error that lists your valid statuses. If an integration relied on the empty list, update it to use a valid status.

What’s Next?

The same error format will be used on more endpoints over time. Matching on the error type and parameter name will keep working as it does.

Pass Reason - Changed

Impact	Pass Reason is now available independently from Compliance and configurable with Business or above. Opting in to Pre-Hire Compliance sets Pass Reason to required to maintain existing behavior.
Severity	Low
Applies To	All organizations with a Business license or above.
Action Required	None required. If you want to Disable or Require a Pass reason you can do so on the Compliance Settings page.
SKU	Business and Higher

Jobs Portal Styling – Changed

Impact	The Jobs Portal has a refreshed look, with rounded edges and minor styling updates. These changes are additive and are designed to work alongside your existing customizations.
Severity	Low
Applies To	All organizations using the Jobs Portal. Organizations with custom CSS in particular.
Action Required	None required for most organizations. If you have added custom CSS to your Jobs Portal, review your portal after the release to confirm it displays as you expect.
SKU	All plans

October 2026 Impact Guide