Kodex Product Update | October 2026

Request Scoring is on for every customer this month, and admins can now set which countries' agencies may send them requests and connect Slack themselves, without going through Support. For EU e-Evidence, notified orders are easier to spot and fewer standard requests arrive flagged as e-Evidence by mistake. Agents get a file hash they can copy straight into their case notes.

Working the queue

Changes for the analysts who work requests every day.

Request Scoring, now for every customer

Every request in your queue now carries a priority of Critical, High, Medium, or Low, with a plain-English reason next to it. Hover over a priority to see which factors drove it. Admins set how much each factor counts with weighting sliders, and a preview shows how the queue would reorder before anything is saved. Teams that accept requests from the United States can also weight by the agency's jurisdiction state. Your dashboard sorts by priority, so the most urgent requests rise to the top.

After a limited launch in September, scoring has been on for all customers since October 8, with default weights that work without any setup. Admins can turn scoring on or off for their organization. Priority scores and their breakdowns are also available in the Kodex API. Read more in the Kodex docs.

The Kodex request dashboard sorted by priority, with a Critical, High, Medium, or Low chip and a plain-English reason on each request, and the breakdown open on a Critical request showing the weighted factors behind its score

A redesigned in-app notifications panel

The Notifications panel, which you open from the left-side menu, has been redesigned. Notifications are grouped by the day they arrived, newest first, and each one shows the request number, the type of update, the time it arrived, and a short description of what happened. Switch between All and Unread to catch up quickly after time away. Open a notification to go straight to its request, dismiss one at a time, or mark them all as read. See "Viewing In-App Notifications" in the Kodex docs for everything that changed.

Clearer country fields in search, columns, and exports

Search filters, dashboard columns, and exports now use the same names for the same data, and clearly separate two fields that were easy to mix up: Requestor Country, where the requesting agent is located, and Requestor Jurisdiction Country Code, the country of the agency's jurisdiction.

Admin controls

New settings admins can manage for their own organization, and one that Kodex Support sets up for you.

Choose which countries can send you requests

Admins can now decide, country by country, which agencies are allowed to submit requests to their organization, with no ticket to Kodex Support. Allowed Jurisdictions replaces the old Allowed Request Location dropdown and its fixed bundles. Pick countries from a searchable list, select a whole region (AMER, EMEA, or APAC) at once, or allow everyone and block a few. A preview such as "40 of 195 jurisdictions are allowed" shows the result before you save.

Your current setting has carried over. If you manage more than one organization, each one keeps its own setting. Agents from a jurisdiction you haven't allowed see a message telling them they aren't authorized to submit to you. Only admins can change this setting. Find it under Settings → Form Settings.

The Allowed Jurisdictions setting under Form Settings, with the EMEA region expanded and a few countries unchecked, and a preview line reading 40 of 195 jurisdictions are allowed

Connect Slack yourself, and move to the new Kodex Slack app by December 31

Admins can now connect Slack to Kodex straight from the portal and decide which notifications go to which channels from the Integration Settings page, with no ticket to Kodex. Use Quick add for a simple rule or Advanced rule for a more specific one. Rules set on a parent organization now apply to its child organizations as well.

If your team already gets Kodex notifications in Slack, move to the new app by December 31, 2026. After that, Kodex will no longer support the old integration. To migrate:

Choose the channels you want notifications in. Your team must own each one, so if Kodex owns your current channel, create a new one first.
Connect the new Kodex Slack app from Integration Settings, then invite it to each channel with /invite @kodex. You may need approval from your Slack admin.
Send a test notification from Integration Settings and confirm it arrives.
Remove the old app, which now shows as "Kodex (Legacy)", and any Kodex users who were added to your channels.

Read the Slack integration guide. Questions? Email help@kodexglobal.com.

An automatic acknowledgment when a request arrives

Kodex can now post a message on new requests automatically, such as "We've received your order and it is being processed." The message appears in the request's activity about 30 seconds after the request comes in, and the requesting agency is notified just as if someone on your team had commented. You choose which requests get it, for example every e-Evidence order or only subpoenas. It never changes the request's status, and each request gets one message at most.

To set it up, contact help@kodexglobal.com. Read more about request rules.

EU e-Evidence

Two months into live orders, this month's e-Evidence changes make notified orders easier to spot and catch mis-flagged submissions earlier.

EA Notified, at a glance

Requests where the Enforcing Authority has been notified now carry an EA Notified chip next to the e-Evidence deadline. It's also a dashboard column you can sort and filter on, and an Advanced Search filter.

Fewer submissions marked e-Evidence by mistake

When an agent marks a manual submission as a European Production Order or European Preservation Order, they now confirm they're attaching the signed Annex I or Annex II form before it goes through. That gives the agent a chance to catch a standard request flagged as e-Evidence by accident, before it reaches your queue. It builds on September's change, which let analysts correct a mis-flagged submission themselves. Live since September 25, with nothing to configure.

An intake setting for e-Evidence-only teams

If your organization only handles EU e-Evidence through Kodex, it can now be set to accept e-Evidence orders only. Agents submitting to you get e-Evidence forms, and other request types are turned away before they reach your queue. Contact your CSM to turn it on.

Kodex API

Additions and fixes for teams that integrate with Kodex.

More of the request in the Kodex API

Internal notes can now be read and written through the Requests API. The list requests endpoint has new filters for request type, legal process, case nature, nondisclosure order, and assignee. Request priority scores and their breakdowns are available too (see Request Scoring above). A subsequent production sent through the API now updates the preservation request it follows: the preservation status changes, the timeline records it, and the production order is linked to the preservation request.

Fixes.

Sending a large number of targets no longer returns an error.
Resending target lookups no longer creates duplicate entries.
Target lookups no longer fail when an organization's types are inherited from its parent organization.
Older files can now be downloaded through the Kodex API following an encryption update.

For law enforcement and government requesters

Everything above is written for provider admins and analysts. This part is for the agencies sending requests in.

A file hash you can copy into your case notes

Every document on your request now shows its SHA-256 hash in the Agent Portal, for files you send and files you receive. Copy the full hash with one click into your evidence log, and you have a record that the file hasn't changed since it arrived. You'll find hashes in View Documents on the request timeline and on the Documents tab. Older files that were uploaded before hashing was added don't show the option. Agents asked for this in training sessions, where their own rules require documented evidence handling.

The View Documents list in the Kodex Agent Portal showing a received file and a sent file, each with its full SHA-256 hash and a copy button

Confirm the signed form when you submit an e-Evidence order

When you submit a European Production Order or European Preservation Order through the portal, you'll now confirm that you're attaching the signed Annex I or Annex II form. The provider receives the form with the order, so there's less back and forth before work starts.

Find a request with part of a name or number

You can now find one of your requests by typing part of the provider's name or part of the request number. You don't need the exact value.

Coming soon

Kodex MCP. We're starting the beta program for the Kodex MCP, which lets customers connect their AI assistant to Kodex and work their queue with our new tools to support prioritizing requests, pulling request details and attachment metadata, and getting agent details on a request. Customer admins control which tools are enabled for their company. The current beta cohort is closed, but if you're interested, reach out and we'll send you the documentation. We expect to open sign-ups again in the near future.

Faster request lists in the Kodex API. A new updatedSince filter on list requests will return only the requests that changed since your last pull, and a faster list implementation with the same search filters as the in-app request dashboard is rolling out.

Resources

The How to Use Kodex guides for the Request Portal, including the request management, notifications, Slack, and request rules pages linked above, are in the Kodex docs.

In Case You Missed It

September's release brought a request audit log feed in the Kodex API, e-Evidence notifications routed by request type and legal framework, Form 3 auto-fill, legal framework on every export, and the how-to guides for the Request Portal.