Highlights of the 2026.1 release across the assistant, administration, and integration areas.
Highlights
Release 2026.1 focuses on the RIKAI assistant, tenant administration, and a documented content API. The table below summarises the changes that require attention from administrators.
| Area | Change | Impact |
|---|---|---|
| Ask RIKAI | Mobile experience with offline draft answers | No action; enabled per tenant |
| Ask RIKAI | Structured feedback with reason codes | Review feedback policy |
| Administration | Custom domain configuration self-service | Requires DNS changes |
| Administration | Data retention schedules per record class | Review defaults before upgrade |
| Integration | Help Content API v1 | Optional; keys issued on request |
| Platform | New APAC South data centre | Optional tenant move |
Upgrade notes
- Review the retention defaults described in Data Retention before the upgrade window; existing tenants keep their previous values, new record classes take the shipped default.
- If you use a custom domain, re-issue the verification record after the upgrade. The old record stays valid for 30 days.
- Integration users should pin the API version segment
v1in every request path.
Nothing in 2026.1 removes an existing API field. Two fields are deprecated and documented as such in the REST API Overview.
Last updated: 2026-09-01